On Mon, Feb 16, 2009 at 09:25:35PM +0000, paul_c wrote:
> On Monday 16 February 2009, Vince Mulhollon wrote:
> > >From Debian Policy Manual version 3.8.0.1, 2008-06-05
> > So the correct Debian location would be /usr/share/doc/emc2/examples/
>
> it was suggested that /usr/share/<whatever> was the correct location. To be
> honest, it doesn't really matter if they go under /usr/share/docs/emc2/
> or /usr/share/emc2.... The only reason change is deemed necessary now, rather
Well, yeah, as far as if it matters or not, technically you can make chips
if you put those files in /tmp or / or /opt or any ole random place. But,
why not do it debian-style if you're going to do debian packages? And if
it is being forced out of the "wrong" place, may as well put it in the
"right" place.
Regarding /usr/share/emc2/ that would be for shared libraries and runtimes
that are not run manually by the end users. If you envision an end user
or a typical sysadmin having any contact with a file, then it doesn't
belong in /usr/share/<packagename>.
See cut and paste from Debian Policy section 8.2
It is recommended that supporting files and run-time support programs
that do not need to be invoked manually by users, but are nevertheless
required for the package to function, be placed (if they are binary)
in a subdirectory of `/usr/lib', preferably under
`/usr/lib/'<package-name>. If the program or file is architecture
independent, the recommendation is for it to be placed in a
subdirectory of `/usr/share' instead, preferably under
`/usr/share/'<package-name>.
Or in summary, to simplify, /usr/share/<package-name> has a big "humans
stay out" sign attached to it, and everyone expects it that way.
Another Debian-way to look at it is you put arch-dependent compiled
libraries in /usr/lib/package/ so you need a place to stash
arch-independent libraries, how bout /usr/share/package/...
There is also some discussion in section 10.7.3 about <package>-configure
scripts that would belong in /usr/share. That's more for internal dpkg
system level config than for user configuration. Like if you had an
emc2-configure script that automagically messed around with RTAI configs
each time the package was installed, err, sort of.
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
