On Dec 5, 2011, at 17:09 , Francis J. Lacoste wrote: > Hi Brad, > > Another alternative would be to put the packaging right into the main > branch. If we want to the Launchpad team maintains this, why require two > pushes, where one will do?
Hi Francis, I was curious about this too and had a chat with Barry last week. He said it was a matter of hygiene that most projects separate their packaging so that it is easier to release to PyPI and other places that don't care about Debian-style packaging. I welcome other opinions. > > Any reason not to set this up on the ~launchpad team itself? That could be done, I just picked ~lazr-developers since that team owns lp:launchpadlib. > > And FWIW, I think this discussion should be happening on launchpad-dev. Of course it should. Thanks for the reminder. --Brad > > Cheers > > On 11-12-05 02:51 PM, Brad Crittenden wrote: >> Hi Francis, >> >> I've created a build recipe for launchpadlib below: >> >> https://code.launchpad.net/~bac/+recipe/launchpadlib-daily >> >> It uses the launchpadlib trunk as the source and a new packaging branch I >> created for the /debian directory. Using this set-up, creating release >> candidate PPA for launchpadlib would require the developer to get the >> packaging branch and update the changelog file, which will be pretty easy >> even for people who don't understand packaging. >> >> If you like this approach, please take the recipe I have and recreate it for >> ~lazr-developers. A new PPA for the team will need to be created and the >> recipe published to it. >> >> --Brad >> >> >> > > -- > Francis J. Lacoste > francis.laco...@canonical.com > _______________________________________________ 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
