Re: Proposed patch management/build solution

2002-01-21 Thread Joel Baker
On Tue, Jan 22, 2002 at 12:39:09AM +, Jonathan Amery wrote: > In article <[EMAIL PROTECTED]> you write: > >EVentually yes, but it may well be that we no longer need this system > >by the time we are stable enough for a formal autobuilder. I'm > >certainly willing to build packages from this tr

Re: Proposed patch management/build solution

2002-01-21 Thread Jonathan Amery
In article <[EMAIL PROTECTED]> you write: >EVentually yes, but it may well be that we no longer need this system >by the time we are stable enough for a formal autobuilder. I'm >certainly willing to build packages from this tree and make them >appear in MIT AFS space, which is web accessible. > I

Re: Proposed patch management/build solution

2002-01-21 Thread Sam Hartman
On Mon, Jan 21, 2002 at 04:17:22PM -0500, [EMAIL PROTECTED] wrote: > On Mon, Jan 21, 2002 at 03:36:01PM -0500, Sam Hartman wrote: > > > "utsl" == utsl <[EMAIL PROTECTED]> writes: > > > > utsl> This is a good idea. I'm interested in it. Why not simply > > utsl> import the standard Deb

Re: Proposed patch management/build solution

2002-01-21 Thread utsl
On Mon, Jan 21, 2002 at 03:36:01PM -0500, Sam Hartman wrote: > > "utsl" == utsl <[EMAIL PROTECTED]> writes: > > utsl> This is a good idea. I'm interested in it. Why not simply > utsl> import the standard Debian source packages as vendor > utsl> branches, and use the normal CVS fa

Re: Proposed patch management/build solution

2002-01-21 Thread Sam Hartman
> "utsl" == utsl <[EMAIL PROTECTED]> writes: utsl> This is a good idea. I'm interested in it. Why not simply utsl> import the standard Debian source packages as vendor utsl> branches, and use the normal CVS facilities to track the utsl> changes? This seems simpler than keepin

Re: Proposed patch management/build solution

2002-01-21 Thread utsl
This is a good idea. I'm interested in it. Why not simply import the standard Debian source packages as vendor branches, and use the normal CVS facilities to track the changes? This seems simpler than keeping patches in separate files, as you describe below. Also, it should work with cvsbuildpacka

Re: Proposed patch management/build solution

2002-01-21 Thread Sam Hartman
> "Joel" == Joel Baker <[EMAIL PROTECTED]> writes: Joel> I'll worry about this when it doesn't require a chroot Joel> tarball just to get things up and running. Until then... the Joel> only folks who're likely to be even remotely interested in Joel> debugging are the diehards,

Re: Proposed patch management/build solution

2002-01-21 Thread Joel Baker
On Mon, Jan 21, 2002 at 12:15:46PM -0500, Sam Hartman wrote: > > > As I mentioned Saturday, I'm interested in helping set up some sort of > system for managing patches that we are not comfortable sending back > to Debian packages yet. > > I'm concerned that without such a system: > > * Differen

Proposed patch management/build solution

2002-01-21 Thread Sam Hartman
As I mentioned Saturday, I'm interested in helping set up some sort of system for managing patches that we are not comfortable sending back to Debian packages yet. I'm concerned that without such a system: * Different people will each set up their own archives of packages with different mecha