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: Core release test bed

mike@i-Connect.Net (Mike Neuffer)  wrote on 22.02.97 in <Pine.LNX.3.95.970222150344.26542k-100000@nomis.i-Connect.Net>:

> On 22 Feb 1997, Kai Henningsen wrote:
>
> > galenh@micron.net (Galen Hazelwood)  wrote on 21.02.97 in
> > <330E94F7.75EAFF0F@micron.net>:
> >
> > > > I would just wish that some people would really as I suggested before
> > > > take a close look at what FreeBSD is doing. Defining an essential core
> > > > system (ca. 60-100MB installed binary size) that contains everything
> > > > an Unix system needs to run _properly_ is an essential step.
> > > >
> > >
> > > I'm not so sure I agree with this...but I'll consider it.
> >
> > We're already doing this. That's about what we call "standard" or better.
>
> BUT this "standard" as you call it is not conflict free. At the mometn you
> can not even on a new install enter the dselect selection screen and leave
> it immediately to install only the "standards". It conflicts immeiately on
> Perl.

Nothing wrong with fixing those bugs - because bugs is what they are.

> The problem with tis sheme is that we need to reorganize the current
> package tree. Essential (standard) packages need to go into one
> directory tree, add-on packages into another, so that you can distinguish
> between them while downloading with CVSUP.

I've been thinking about this for a while. Currently, my ideas are about  
as follows:

/debian
  /.releases                                  [0]
    /<codeword>
      /{core,addon,contrib,non-free}          [1]
        /{binary-*,source}
          /<section>                          [2]

  /Debian-<version>          -> releases/<codeword>
  /{stable,unstable,fixed}   -> releases/<codeword>


[1] Conceptually, "non-US" fits here, except that for ftp server  
management reasons, it probably is a lot better off in a completely  
separate tree. "local" also fits here, but again ...

[2] *If* there is a base section, it is only in .../core/..., but even  
there, it may be better to do without.

************

[0] Keep the root directory small! No need to keep all the release  
directories there. Optimally, the root would have about 20 directory  
entries or less, so it has a good chance of fitting on one screen.


MfG Kai


--
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