DragonFly BSD
DragonFly kernel List (threaded) for 2003-10
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: variant symlinks (was Re: Anybody working on removing sendmail from base?)


From: Mike Porter <mupi@xxxxxxxxx>
Date: Mon, 6 Oct 2003 00:45:46 -0600

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 04 October 2003 12:52 pm, Hiten Pandya wrote:
> Sander Vesik wrote:

>
> 	Hmm, 47 different versions of the same *ONE* software is what we
> 	are limiting ourselves with at the moment.  But if you think
> 	about this in a recurring way, we could end up using a lot of
> 	disk space, wether we hide it or not.
>
Agreed.  Nobdoy was seriously considering that anybody would actually have 
that many, although it could be theoretically possible given sufficient disk 
space.

> 	From what it looks, the whole idea does not space conservative,
> 	but heck, prove me wrong I say. 8-)
>
The idea is not necessarily to conserve disk space, but to make the 
appropriate tools available, if necessary.  This is why I think the option to 
remove packages which are installed as a 'compile time' dependency is a Good 
Idea.

> 	In a scenario where you need to install a package which has
> 	multiple dependancies, with sub-deps, it is going to result
> 	in a huge mess.  I am assuming that the sub-deps will have
> 	their own particular dependancy requirments thus giving us
> 	lots of packages.  Hiding them will not make any difference
> 	space wise.
>
This is a potential issue, however, most often, when a library is upgraded, it 
retains backwards compatibility with previous versions. the trick is to be 
able to know which ones actually do this, and create a 'range' of acceptable 
dependencies ("this package requires glibc version 6.2 or greater" for 
example, or "this package requires glibc version 5.4-6.8".    Only if glibc 
exceeds 6.8 would there be a need for two copies of glibc...and chances are 
there may be a program with a max version of 5.6, and we can kill two birds 
with one stone by having glibc 5.6.  the logic for determining this, of 
course, must be provided by the ports system, and has no real bearing on the 
underlying framework.


mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE/gQ+eY30jZzkECLcRAvJQAJ0Zr7F2eIvJ83fB0sljRooXYUu29ACfW/zY
2yn3JUNqdd9kzRnJ7I82Zdk=
=qMAx
-----END PGP SIGNATURE-----





[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]