Re: why apt/dpkg not using bzip2
On Sun, Sep 10, 2000 at 07:43:07PM -0700, Joey Hess wrote:
> Ben Collins wrote:
> > > It doesn't matter if it's user-friendly. The DBS package format is not
> > > developer-friendly.
> > But it's maintainer friendly, and that is far more useful for us to have
> > good packages.
> I was using developer in the sense of "debian developer".
> However, friendlyliness for users is equally important.
Still, documentation. Dpkg-source isn't friendly without documentation.
> > FWIW, before I started using a DBS based source format, I sat down many
> > times to try and upgrade my packages to new upstream source and was so
> > frustrated with forward porting patches that it sat for weeks or even
> > months at a time before I got enough time/energy to do so. Example:
> > getting openldap2 ready took all of 30 minutes. This included forward
> > porting each patch. With the old format, I would have either manually went
> > throught the diff.gz, or run the patch and went through each .rej. My time
> > was saved, which makes the package more up-to-date, better maintained, and
> > needs less attention.
> I'll bet I can get better results using cvs than are possible with DBS.
Maybe you can, because that is what you prefer. I don't feel like setting
up a CVS repo to do my package maintainence, since that means I tie myself
down to one machine, or have to setup ssh or pserver so I can work on it from
anywhere, and that assumes I have a net accessible development system.
Sorry, but that's just not possible for most folks. I bet I get better
results with what I have, since I use it day-to-day, and it does
everything I need to do. I already have a new README.build that I am
putting in all my packages, which will document how I have things setup.
That takes away most of the problems.
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` email@example.com -- firstname.lastname@example.org -- email@example.com '
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com