[gentoo-dev] Re: Handling multiple packages providing the same convenience symlink

[Alexander Skwar]

Stephen Bennett wrote:
> Erm, this should have gone to the list... sorry ciaranm. :/
>
> On Thu, 2004-11-04 at 18:21 +0000, Ciaran McCreesh wrote:
>> Something like:
>>
>> # eselect --set vi vim
>> # eselect --set kernel linux-2.6.7
>> # eselect --set gcc sparc-unknown-linux-gnu-3.3.4
>>
>> and:
>>
>> # eselect --list kernel
>> linux-2.6.7      (*)
>> linux-2.6.8.1
>> linux-2.6.10_rc1
>>
>> and:
>>
>> # eselect --list
>> gcc              sparc-unknown-linux-gnu-3.3.4
>> kernel:          linux-2.6.7
>> vi:              /usr/bin/vim
>
> I'm liking the idea, but it needs a bit more thought...for example, what
> happens when we have vim and nvi wanting to install /usr/bin/vi as a
> symlink, and the freebsd system ebuilds wanting to install /usr/bin/vi
> as a binary? Some naming scheme is going to be needed to get binaries
> like that out of the way.

Here again the Debian way has solved it: There would be no
/usr/bin/vi, but only a binary called /usr/bin/vi.vim, vi.nvi and
so on. With FEATURE="collision-protect", the collision of some old,
not yet converted package wanting to install /usr/bin/vi would
be easily detected.

> things-- appending the package name could get ugly, so it might be best
> to let the ebuild define a string to append, which could easily be set
> to version, package name, or something arbitrary.

Yes. Something arbitrary, defaulting to something like packageName_version,
would be good :)

Alexander Skwar
-- 
A company is known by the men it keeps.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯


--
gentoo-dev@g.o mailing list