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: New updated "1.2 installation problems" list.

On 28 Dec 1996, Darren/Torin/Who Ever... wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> 
> Dale Scheetz, in an immanent manifestation of deity, wrote:
> >As best I can tell from the report, perl (or someone) removes the link
> >during pre-install and later puts it back during post-install. In between
> >time packages that wish to use run perl via /bin/perl have their
> >per-install scripts fail because of this missing link.
> 
> Yep.  I remove it during the prerm and reinstall it in the postinst.
> We don't want a dangling /bin/perl if they don't re-install.  If a
> package tries to use /bin/perl in their install scripts, they are broken
> and should have bugs registered against them.  I'd really like to remove
> the /bin/perl symbolic link but people still seem to need it.
> 
This is the result of the way that dselect installs packages. As the
distribution has become larger this problem has become more ugly.
I would argue (as I believe some others have done so before me) that
installation scripts should be REQUIRED to be shell scripts and that they
expect to be run under a Bash shell. Bash is the default shell for Debian,
and even on systems where it is not the default, installers could be made
to understand that they must run Debian installation programs under Bash. 
It's been a while since I actually read through the Policy/Programmer
manuals, but my memory was that shell scripting was the preferred method
and that other languages were HEAVILY discouraged.
In order for installation to go smoothly with any other scripting
language, the package using it in its scripts would need to pre-depend on
the scripting package. But, pre-depends were intended ONLY for essencial
packages, and it's not clear how well they are currently implimented.
Seems the best way to deal with this is to submit bugs against all
packages that use something other than #!/bin/sh in their installation
scripts.
Can we get a verification of the policy on this?

Luck,

Dwarf

------------                                          --------------

aka   Dale Scheetz                   Phone:   1 (904) 877-0257
      Flexible Software              Fax:     NONE 
      Black Creek Critters           e-mail:  dwarf@polaris.net

------------ If you don't see what you want, just ask --------------


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