The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unidentified subject!

On Thu, 20 Feb 1997, Bruce Perens wrote:

> many reasons. We could abandon this deb-make/dpkg/dselect sillyness. We
> could be using the package system that Red Hat, Caldera, and
> _EVERY_OTHER_ Linux distribution that has a package system is using
> now. We could have the capability for those other distributions to use
> Debian packages, and for us to directly install their packages without
> kludges like "alien". We could immediately have a better
> package-selection user interface. We could have _one_ kind of
> dependency, instead of 4 (soon 5 if we are to implement "Breaks:").

That is a major design issue in dpkg.

> What we are doing now is going off in our own non-standard direction
> and continuing to re-invent our own invention. Red Hat did the package
> system better, and simpler, than we did, and the entire rest of the
> Linux world has adopted their work. Who else is using dpkg?

.deb packages are simpler than .rpm packages by their very nature. Some
of the dependency things went the wrong way though.

.deb packages can easily be unpacked on any system. That universality has
never been really pushed and clarified. RPM packages have a complex binary
structure and still have problems with configuration files.

> Rather than talk about re-inventing deb-make, we should be exploring
> how to convert deb-make packages to RPM ones automaticaly.

That is probably easy to do with debmake. RPM does not have all the
framework and the standards we have which are one of the major strenghts
of the project.

> Guys, we lost the fight. It's time to admit it.

I do not think so. Lets attack the problem. Split up dpkg into multiple
packages to be maintained and independantly developed.

We could have

dpkg = base dpkg

dselect = Selection interface

dpkg-dev = Development package

debian-standards = Policy etc etc.


--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
Please always CC me when replying to posts on mailing lists.


--
Please respect the confidentiality of material on the debian-private list.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com