[prev in list] [next in list] [prev in thread] [next in thread] 

List:       miros-discuss
Subject:    @lib (in PLISTs) considered harmful
From:       Thorsten Glaser <tg () mirbsd ! de>
Date:       2008-08-12 16:14:39
Message-ID: Pine.BSM.4.64L.0808121612570.31002 () herc ! mirbsd ! org
[Download RAW message or body]

@lib lib/python${MODPY_VERSION}/site-packages/_omniidlmodule.so.4.1

This won't do: On MirBSD, the files
│lib/python${MODPY_VERSION}/site-packages/_omniidlmodule.so
│lib/python${MODPY_VERSION}/site-packages/_omniidlmodule.so.4
│lib/python${MODPY_VERSION}/site-packages/_omniidlmodule.so.4.1
exist, the first two are symbolic links. However, as these are bundles,
no dylibs, they're tried to be opened as _omniidlmodule.so (only, because
this is Python's own dynamic loader). The PLIST generator contracts these
to @lib as per GNU dyld naming spec, and BSD dyld naming spec is used on
package installation, which prevents the symbolic links from being recreated.

//mirabilos
-- 
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting all the prepositions
in English text in bold font.	-- Rob Pike in "Notes on Programming in C"

[prev in list] [next in list] [prev in thread] [next in thread]