Thoughts on Multi-Symlink Concept

[Jason Hellenthal]

That is a rather lovely example. Going a bit beyond my initial thoughts. . . . this could be really handy if done correctly. For ports, source, object tree's . . . obviously bin directories and even lib directories. Call it the poor-mans replication system but with some pretty big benifits.

My initial thoughts were to just point directly to files, excluding using globing as a way to just include files in a massive config sort of fashion but if globing comes into play that would be awesome.

-- 
 Jason Hellenthal
 Voice: 95.30.17.6/616
 JJH48-ARIN

> On Feb 16, 2014, at 0:16, perryh at pluto.rain.com (Perry Hutchison) wrote:
> 
> Jordan Hubbard <jordan.hubbard at gmail.com> wrote:
> 
>> Even variant symlinks (/bin -> /${ARCH}/bin), which can expand
>> differently depending on the user context, have clearly
>> understandable semantics - you know that the symlink is going
>> to expand to exactly one file no matter what ARCH is set to.
> 
> s/file/pathname/
> 
> Depending on what ARCH is set to, the expanision may or may not
> point to any actual file (or directory, or ...)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6118 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20140216/680353ca/attachment.bin>