DragonFly users List (threaded) for 2005-08
Re: Compatability with FreeBSD Ports [debian package tools]
> <4303571D.9050306@xxxxxxxxxxxxx> <43036a16$0$739$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200508171711.j7HHBPi1021543@xxxxxxxxxxxxxxxxxxxx> <43037ca7$0$740$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <430380CF.7040703@xxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Trace: 1124321948 crater_reader.dragonflybsd.org 742 18.104.22.168
Xref: crater_reader.dragonflybsd.org dragonfly.users:3866
Gabriel Ambuehl wrote:
> Long story short: the perfect system doesn't yet exist. OSX .app
> approach comes close but is totally different paradigm and not really
> what a BSD should be after.
While strictly copying MacOSX is not an option, our dream package
management system should allow us to install an application and all its
dependencies in its own directory, possibly with its own config space.
This would be called "standalone" application, maybe.
/usr/standalone/apache-2/bin ./etc ./lib ...
possibly, an option would have it installed in such a way that it is
ready to be chrooted (maintaining a copy of the necessary system libraries)
This way, it is possible to separate important applications from the
other stuff. Then you gain peace of mind. You can use apps such as
portupgrade -a on the non important stuff and manage each critical app
separatedly, which makes them much less dangerous to upgrade by the way.
Disk space is cheap so I don't mind the duplication of libraries caused
by such a scheme.
And when you want to clean the mess, you just drag the app to the Trash
. .. er ... cp -R <pathtoappdir>.
are views something like this?
please be kind, I am far from understanding the subject