[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU System Explanation
From: |
Barry deFreese |
Subject: |
Re: GNU System Explanation |
Date: |
Sat, 11 Feb 2006 20:28:55 -0500 |
This didn't seem to go through the first time??
Barry deFreese (aka bddebian)
----- Original Message -----
From: "Barry deFreese" <address@hidden>
To: <address@hidden>
Sent: Saturday, February 11, 2006 1:56 PM
Subject: GNU System Explanation
Folks,
Can someone please give me a concise explanation of what the intended
goals are here?
I understand that you want packages isolation in /packages, but why?
Managing multiple versions of a package could potentially become a
headache I believe.
For example: I have /packages/foo-1.1/bin/foo and /lib/libfoo. Then I
install foo-1.2 which has /packages/foo-1.2/bin/foo and /lib/libfoo,
foo-1.1 becomes pretty much unusable anyway, does it not?
I also understand that you have philosophical differences with Debian.
Fine, but Debian provides a nice set of tools for package management when
dealing with things like dependencies, reverse dependencies, etc. Yes, it
would be nice to be able to use common filesystem commands to install and
manage packages but is it realistic? If I extract foo-1.1.tar.gz to
/packages/foo but foo needs bar to run now what? OK, so I extract
bar-1.0.tar.gz to /packages/bar. But now I install baz which also depends
on bar, there becomes 1 to many and potentially many to 1 relationships of
packages.
What do people see as currently wrong with dpkg other than being Debian
and a little cumbersome for developers?
Can someone please enlighten me?
Thank you,
Barry deFreese (aka bddebian)
Re: GNU System Explanation, Alfred M\. Szmidt, 2006/02/12
Re: GNU System Explanation, Gianluca Guida, 2006/02/12
Re: GNU System Explanation,
Barry deFreese <=