launchpad-dev team mailing list archive

[Aaron Bentley <aaron@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-06-20 03:32 PM, Jelmer Vernooij wrote:
> Hi Launchpadders,
> 
> I would be interested to hear feedback on
> https://dev.launchpad.net/LEP/BuildFromBranchIntoArchive

It's surprising to see this LEP.  Considering that we support recipes,
and building from a branch is a trivial case of building from a recipe,
it seemed natural to do it that way.  In fact, we you create a recipe,
you get a default recipe that builds from a branch.

I would like a much more thorough explanation of:

  Using recipes as they currently exist may make the linkage between
  source package branch and built source package much looser.

I don't understand this:

  It seems like locking the source package branch to the branch makes
  it easier to find the right source for a package, and easier to get
  the right access control.

It seems like you're assuming recipes are stored as text, but they're
not.  They provide foreign key references to branches.  So it's very
easy to find the right source for a package.

I disagree with this:

  We can generate manifests on demand from a SourcePackageBranchBuild
  if users need them, there's no need to store them in the database

Manifests provide traceability, like logs.  Users may not know they need
them until days or weeks after they've performed the build.

- From the LEP, it's not clear that the benefits are valuable enough to
justify having two ways of doing basically the same thing.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3/qakACgkQ0F+nu1YWqI39EQCeM65IBMFxWf4l3vLat3CFc/iZ
pGMAnAgHWrVw1ny62V5qHm630GnOJFUz
=icpR
-----END PGP SIGNATURE-----