[Pkg-shadow-devel] What is the next step for shadow in debian?
Nicolas François
nicolas.francois@centraliens.net
Wed, 8 Jun 2005 22:31:22 +0200
On Wed, Jun 08, 2005 at 05:03:35PM +0200, Martin Quinson wrote:
> On Wed, Jun 08, 2005 at 03:14:20PM +0200, Nicolas François wrote:
> > On Wed, Jun 08, 2005 at 11:03:54AM +0200, Martin Quinson wrote:
> > > Hello,
> > >
> > > I am wondering whether we want to do another release on 4.0.3 to cl=
ose yet
> > > another bunch of bugs, or whether we want to move to the lastest up=
stream
> > > release.
> > >
> > > I'm in favor of the second, but we have to all agree on this becaus=
e the
> > > move will be somehow tedious and it will be difficult to have sever=
al person
> > > doing it. If the others change the patchset at the same time, it'll=
be
> > > *very* difficult to do.
> >
> > I would love to play with a pre-experimental package at Debconf (upst=
ream
> > shadow packaged, with the infrastructure to add patches).
> >
> > Also, I'm ready to bribe anyboby comming to Debconf with a ginger or =
fir
> > needle liquor bottle.
>
> What do you mean with playing with such a package? Trying to do it your=
self,
> or discovering the work of someone else (being, I guess, me or Alex)?
I would like to try 4.0.9, and this would be much easier with a package.
Thus I first need a debian directory, but not necessarily any of the
current Debian patches (that will be part of the game;)
The current debian directory can probably be used, with an empty "series".
So, thinking a little more, what is needed is just to decide how to
proceed.
* copy the trunk to a "4.0.3" branch for development in sid
* use the trunk for the 4.0.9 package
(the 4.0.3 branch can evolve. We will just have to use 'svn diff' with
its original revision
or
* copy the trunk to an "experimental" branch that we could merge later
with the trunk when the package will be uploaded to unstable.
Best Regards,
--
Nekral