+1 on moving RPM/DEB meta data into the main source tree. (Jan, these tools expect specific top level dirs/files, but they're usually self-contained. As you say, we can change things if it gets cluttered.)
Benoit, what about maintaining rpms/debs on Apache infra? Is there any reason we'd want to use Ubuntu PPAs, when we can just set up an APT repository with something like reprepro, and stick it on dist.apache.org. On 22 May 2013 09:06, Benoit Chesneau <[email protected]> wrote: > On Tue, May 21, 2013 at 8:54 PM, Randall Leeds <[email protected]> > wrote: > > > I had been using git-buildpackage tools to maintain debian, upstream, > > and pristine-tar branches. I was doing this all from my local couchdb > > repo. I don't know whether or not it makes sense to push all this to > > apache git or not, but I would love to collaborate this way. I find > > the gbp (git buildpackage) tools to be pretty helpful now that I'm > > used to it. > > Think it would be definitely a good idea to have all the tooling in > the main repo. How did you hook the result to launchpad though? > > - benoit > -- NS
