In message <[EMAIL PROTECTED]> you wrote:
>> "Dima" == Dima <[EMAIL PROTECTED]> writes:
>
>>> As you state, disk space is now pretty cheap. That's not an
>>> excuse to wantonly waste disk a la Microsoft, but symlinks
>>> aren't exactly huge.
>
>Dima> Which is even worse, in a s
> "Dima" == Dima <[EMAIL PROTECTED]> writes:
>> As you state, disk space is now pretty cheap. That's not an
>> excuse to wantonly waste disk a la Microsoft, but symlinks
>> aren't exactly huge.
Dima> Which is even worse, in a sense -- they waste a whole disk
Dima> block e
On 7 Apr 1997, Alair Pereira do Lago wrote:
> " Raymond A. Ingles" <[EMAIL PROTECTED]> writes:
>
> > Installed packages go to a specific place in the file hierarchy, e.g.
> > "/usr/packages//". There's "/usr/packages//lib/",
> > "/usr/packages//bin/", etc. A script then makes symlinks from, say,
In message <[EMAIL PROTECTED]> you wrote:
...
>>Ok, the alternative is that the script uses the information provided
>>inside the package, which is precisely what we have now [...]
>
> With the exception that the package doesn't muck with the rest of the
>filesystem directly. It has to go through a
On Sun, 6 Apr 1997, Dima wrote:
>...
>Aint that simple -- the standard debian-provided script released
>yesterday has to know how to handle a new package I will release
>tomorrow. [...]
Well, actually, my description wasn't entirely complete. The idea is,
you have a set of directories that speci
On Sat, 5 Apr 1997, John Foster wrote:
>I see a couple of problems:
>
>From a users perspective the clourisation option for ls will be close to
>useless, as almost everything under /usr will be pale blue.
Unless you use "ls -L". Not to be pedantic (honest!), but from the
man page:
---
-L
" Raymond A. Ingles" <[EMAIL PROTECTED]> writes:
> Installed packages go to a specific place in the file hierarchy, e.g.
> "/usr/packages//". There's "/usr/packages//lib/",
> "/usr/packages//bin/", etc. A script then makes symlinks from, say,
> "/usr/lib/" to "/usr/packages//lib/".
What about pe
In message <[EMAIL PROTECTED]> you wrote:
>
...
> If we use the "/usr/packages/*" method, though, we can separate
>installation into two steps. The maintainer supplies normal install
>scripts that handles everything under "/usr/packages//".
>It runs as, say, user "tool", group "bin". After that's f
Hi,
May I remind people that Debian does not depend on any
de-install scripts written by package developers, which could have
bugs and throw the whole system into chaos (which is just one of the
reasons behind the desire to have a secure package installation).
So, deinstallatio
I see a couple of problems:
>From a users perspective the clourisation option for ls will be close to
useless, as almost everything under /usr will be pale blue. I think that
ls will have to be modified to set the colour based on the links source
- but then how do you identify the symlinks that yo
There's been some discussion on the list lately about the possibility
of secure package installation, and whether it's possible, desirable,
or practical. Secure installation of Unix software can be complicated,
but there are some principles that can simplify things and make it
less error-prone an
11 matches
Mail list logo
