On Tue, 2011-06-21 at 09:15 -0400, Curtis Hovey wrote: > On Mon, 2011-06-20 at 23:17 +0200, Jelmer Vernooij wrote: > > Recipes are very useful for doing regular builds from a combination > > of > > multiple branches into a PPA (like daily builds). They're less > > appropriate for manual builds into an archive. > Is this feature just about source package branches? They are only > branches that I know that are guaranteed to have a debian/ directory. It's not technically tied to package branches, although most branches with a debian/ directory would be package branches.
Like with a recipe that doesn't create a debian/ directory, if you request a build of a branch without a proper debian/ directory that build would simply fail. > Is the goal just to rebuild a package in an archive to ensure deps are > met and that build links to changed binaries? The main use case is allowing people to prepare a package branch and to immediately get that built, rather than having to locally create a source package and dput that. The other LEP that I mentioned discusses doing this for the main archive too, so Ubuntu developers can simply update a bzr branch to upload to the primary archive. Cheers, Jelmer
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
