Vince Mulhollon wrote:

>On Mon, Feb 16, 2009 at 01:02:33PM +0000, paul_c wrote:
>  
>
>>Read the LFSH - /usr/share/doc is for miscellaneous documentation - Sample 
>>configuration files are not "documentation". If you use standard packaging 
>>tools and conventions, the sample configuration files would be installed 
>>in /usr/share/<package name>/
>>    
>>
>
>Don't know what the LFSH is.
>  
>
Linux FileSystem Hierarchy, I think.  Part of the LSB (Linux Standard 
Base) project maybe.

>This situation is handled explicitly by Debian Policy, section 12.6 Examples
>
>     Any examples (configurations, source files, whatever), should be
>     installed in a directory `/usr/share/doc/<package>/examples'.  These
>     files should not be referenced by any program: they're there for the
>     benefit of the system administrator and users as documentation only.
>     Architecture-specific example files should be installed in a directory
>     `/usr/lib/<package>/examples' with symbolic links to them from
>     `/usr/share/doc/<package>/examples', or the latter directory itself
>     may be a symbolic link to the former.
>
>>From Debian Policy Manual version 3.8.0.1, 2008-06-05
>
>So the correct Debian location would be /usr/share/doc/emc2/examples/
>  
>
We have two kinds of example: configurations and gcode.  Do you think 
that both should go under usr/share/doc?

There are other examples as well I think, like (classic)ladders, some 
scripts (like jdi.py), maybe even skeleton code for writing your own HAL 
components.  Do you think these should all be considered examples in 
this context?

Thanks
- Steve


------------------------------------------------------------------------------
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

Reply via email to