where do scripts go?
Section 10.4 of the policy discusses scripts but doesn't say where they belong. I'm writing a GUI app that displays a list of scanned files and has some U/I bits to help me choose what folder it goes to, the date associated with it, c., and then I press a button and move and rename the file. The rules for what validating the users input and the actual mechanism for renaming files is highly site-specific, so I'm going to split out that logic into a perl script which will communicate with the GUI via ordinary pipes. It will not make sense to run this script seperately. The user will be able to specify an alternate script on the command line. Where does this script belong? /usr/bin, /var/lib/package, /usr/share/package ? This is probably in the policy but I missed it.
Re: where do scripts go?
On Sun, Jul 11, 2004 at 05:56:05AM -0700, William Ballard wrote:
I'm writing a GUI app that displays a list of scanned files and has some
U/I bits to help me choose what folder it goes to, the date associated
with it, c., and then I press a button and move and rename the file.
The rules for what validating the users input and the actual mechanism
for renaming files is highly site-specific, so I'm going to split out
that logic into a perl script which will communicate with the GUI via
ordinary pipes. It will not make sense to run this script seperately.
The user will be able to specify an alternate script on the command
line.
Where does this script belong? /usr/bin, /var/lib/package,
/usr/share/package ?
OK, The first distinction we'll make is between intent to modify. Not
intended for modification in the normal course of use? It lives somewhere
in /usr. Modification by admin is /etc, and modification by package usually
means /var/lib. If we're modifying, that's about it. Note that you'll
ordinarily want to split the modifiable portion of a script into a separate
file, so a portion of it might follow the rules below, whilst the modifiable
remainder would follow the above rules.
From there, we look at execution by user. Yes? /usr/{s,}bin. No? Is it
architecture dependent or independent -- that is, should the exact same file
contents be comprehensible on all architectures? If it's architecture
dependent, /usr/lib it goes. Independent stuff in /usr/share.
Most of those get a package name appended, for namespace protection.
This is probably in the policy but I missed it.
Possibly, but I think it's a bit more spread out. And, as you can see, the
rules aren't exactly straightforward -- nor are they necessarily set in
stone exactly as I've detailed them above. I'm sure someone will come up
with alternative strategies.
- Matt
Re: where do scripts go?
On Sun, Jul 11, 2004 at 11:08:50PM +1000, Matthew Palmer wrote:
From there, we look at execution by user. Yes? /usr/{s,}bin. No? Is it
architecture dependent or independent -- that is, should the exact same file
contents be comprehensible on all architectures? If it's architecture
dependent, /usr/lib it goes. Independent stuff in /usr/share.
Most of those get a package name appended, for namespace protection.
Based on my needs, I think these perl scripts belong in
/usr/share/package. I didn't know if it was permitted to have
executable scripts in /usr/share. I guess it is.
Thanks!
Re: where do scripts go?
On Sun, Jul 11, 2004 at 05:56:05AM -0700, William Ballard wrote: Where does this script belong? /usr/bin, /var/lib/package, /usr/share/package ? This is probably in the policy but I missed it. See the FHS, which is included in policy by reference. -- Steve Langasek postmodern programmer
Ask for mentor and advices
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I build some packages and I'd like to know my mistakes and how to improve them or others. The packages I made may be useful for others. The first package I'd like to upload is qmail-scanner. First from http://qmail-scanner.sourceforge.net/ The package I build is there for apt deb http://debian.i-connexion.net/ woody icx/qmail-scanner deb-src http://debian.i-connexion.net/ woody icx/qmail-scanner I know that the qmail depends can't be satisfied right now, but as for vpopmail I may remove it. Thanks. - -- Pascal Greliche 10, rue Guillaume d'Autignac Résidence Le Mas Drevon Bat F9 34070 Montpellier France Tel : +33 4 67 68 44 58 Cel : +33 6 15 02 03 36 e-mail : [EMAIL PROTECTED] ICQ : 13705677 MSN : [EMAIL PROTECTED] Yahoo : pouet78 AIM / .mac : Pouet78 Network and Systems Administrator ICX France 121, rue du Caducée 34195 Montpellier France e-mail : [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFA8Zo/NB5xCNYOs7cRAqhZAJ99JbL+L0iVtoOar65O0eN/G2LroACfZCkd RSRcbZpmcGWZh+7bz+QqgpI= =0HPU -END PGP SIGNATURE- -- Pascal Greliche Service Technique ICX France Tel : 08 99 703 403 Fax : 08 26 800 206
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Replying to my own mail yesterday (again) no-traffic-bug which caused no-graphing-possible (skipping current run) fixed... (My suspicion than something more was broken was probably just because I was in a hurry and didn't notice that I've configured the subnet wrong.) Will submit this to the bandwidthd patch tracker at sourceforge. David: please continue with the review/merge... http://fjortis.info/pub/debian/bandwidthd-1.2.1/upstream/ New debian package 1.2.1b-14 which includes this fix and some other changes suggested by Eduard Bloch. Eduard: could you please test this new version (and investigate why bandwidthd doesn't pick up any packets on your system, possible subnet configuration error). http://fjortis.info/pub/debian/bandwidthd-latest/ Regards, Andreas Henriksson
Re: where do scripts go?
On Sun, Jul 11, 2004 at 01:15:55PM -0500, Steve Langasek wrote: On Sun, Jul 11, 2004 at 05:56:05AM -0700, William Ballard wrote: Where does this script belong? /usr/bin, /var/lib/package, /usr/share/package ? This is probably in the policy but I missed it. See the FHS, which is included in policy by reference. Do nonmodifiable perl scripts never intended to be directly launched by the user count as data ? My program will be called tufiler, and will have the supporting scripts demo.pl and tufiler.pl. Demo.pl will just throw up a fake file list and not actually move or rename any files, so people can get the idea of what the program does. tufiler.pl will be *my* idea of how to file scanned papers, and there's a high liklihood people will want to modify the logic. I figured people would just make a copy and specify the alternate perl script on the command line. So I can do (1) /usr/bin/tufiler-demo.pl /usr/bin/tufiler.pl (2) /etc/tufiler/tufiler.pl, /usr/share/tufiler/demo.pl (3) /usr/share/tufiler/tufiler.pl, /usr/share/tufiler/demo.pl Remember, people will never run these scripts directly. I guess maybe they belong in /etc.
Re: where do scripts go?
William Ballard wrote: My program will be called tufiler, and will have the supporting scripts demo.pl and tufiler.pl. Demo.pl will just throw up a fake file list and not actually move or rename any files, so people can get the idea of what the program does. tufiler.pl will be *my* idea of how to file scanned papers, and there's a high liklihood people will want to modify the logic. I figured people would just make a copy and specify the alternate perl script on the command line. In that case, it's common to place the original script in /usr/share/doc/PACKAGE/examples, with instructions for the user to make a customized copy before using it.
where do scripts go?
Section 10.4 of the policy discusses scripts but doesn't say where they belong. I'm writing a GUI app that displays a list of scanned files and has some U/I bits to help me choose what folder it goes to, the date associated with it, c., and then I press a button and move and rename the file. The rules for what validating the users input and the actual mechanism for renaming files is highly site-specific, so I'm going to split out that logic into a perl script which will communicate with the GUI via ordinary pipes. It will not make sense to run this script seperately. The user will be able to specify an alternate script on the command line. Where does this script belong? /usr/bin, /var/lib/package, /usr/share/package ? This is probably in the policy but I missed it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: where do scripts go?
On Sun, Jul 11, 2004 at 05:56:05AM -0700, William Ballard wrote:
I'm writing a GUI app that displays a list of scanned files and has some
U/I bits to help me choose what folder it goes to, the date associated
with it, c., and then I press a button and move and rename the file.
The rules for what validating the users input and the actual mechanism
for renaming files is highly site-specific, so I'm going to split out
that logic into a perl script which will communicate with the GUI via
ordinary pipes. It will not make sense to run this script seperately.
The user will be able to specify an alternate script on the command
line.
Where does this script belong? /usr/bin, /var/lib/package,
/usr/share/package ?
OK, The first distinction we'll make is between intent to modify. Not
intended for modification in the normal course of use? It lives somewhere
in /usr. Modification by admin is /etc, and modification by package usually
means /var/lib. If we're modifying, that's about it. Note that you'll
ordinarily want to split the modifiable portion of a script into a separate
file, so a portion of it might follow the rules below, whilst the modifiable
remainder would follow the above rules.
From there, we look at execution by user. Yes? /usr/{s,}bin. No? Is it
architecture dependent or independent -- that is, should the exact same file
contents be comprehensible on all architectures? If it's architecture
dependent, /usr/lib it goes. Independent stuff in /usr/share.
Most of those get a package name appended, for namespace protection.
This is probably in the policy but I missed it.
Possibly, but I think it's a bit more spread out. And, as you can see, the
rules aren't exactly straightforward -- nor are they necessarily set in
stone exactly as I've detailed them above. I'm sure someone will come up
with alternative strategies.
- Matt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: where do scripts go?
On Sun, Jul 11, 2004 at 11:08:50PM +1000, Matthew Palmer wrote:
From there, we look at execution by user. Yes? /usr/{s,}bin. No? Is it
architecture dependent or independent -- that is, should the exact same file
contents be comprehensible on all architectures? If it's architecture
dependent, /usr/lib it goes. Independent stuff in /usr/share.
Most of those get a package name appended, for namespace protection.
Based on my needs, I think these perl scripts belong in
/usr/share/package. I didn't know if it was permitted to have
executable scripts in /usr/share. I guess it is.
Thanks!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: where do scripts go?
On Sun, Jul 11, 2004 at 05:56:05AM -0700, William Ballard wrote: Where does this script belong? /usr/bin, /var/lib/package, /usr/share/package ? This is probably in the policy but I missed it. See the FHS, which is included in policy by reference. -- Steve Langasek postmodern programmer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Ask for mentor and advices
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I build some packages and I'd like to know my mistakes and how to improve them or others. The packages I made may be useful for others. The first package I'd like to upload is qmail-scanner. First from http://qmail-scanner.sourceforge.net/ The package I build is there for apt deb http://debian.i-connexion.net/ woody icx/qmail-scanner deb-src http://debian.i-connexion.net/ woody icx/qmail-scanner I know that the qmail depends can't be satisfied right now, but as for vpopmail I may remove it. Thanks. - -- Pascal Greliche 10, rue Guillaume d'Autignac Résidence Le Mas Drevon Bat F9 34070 Montpellier France Tel : +33 4 67 68 44 58 Cel : +33 6 15 02 03 36 e-mail : [EMAIL PROTECTED] ICQ : 13705677 MSN : [EMAIL PROTECTED] Yahoo : pouet78 AIM / .mac : Pouet78 Network and Systems Administrator ICX France 121, rue du Caducée 34195 Montpellier France e-mail : [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFA8Zo/NB5xCNYOs7cRAqhZAJ99JbL+L0iVtoOar65O0eN/G2LroACfZCkd RSRcbZpmcGWZh+7bz+QqgpI= =0HPU -END PGP SIGNATURE- -- Pascal Greliche Service Technique ICX France Tel : 08 99 703 403 Fax : 08 26 800 206
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Replying to my own mail yesterday (again) no-traffic-bug which caused no-graphing-possible (skipping current run) fixed... (My suspicion than something more was broken was probably just because I was in a hurry and didn't notice that I've configured the subnet wrong.) Will submit this to the bandwidthd patch tracker at sourceforge. David: please continue with the review/merge... http://fjortis.info/pub/debian/bandwidthd-1.2.1/upstream/ New debian package 1.2.1b-14 which includes this fix and some other changes suggested by Eduard Bloch. Eduard: could you please test this new version (and investigate why bandwidthd doesn't pick up any packets on your system, possible subnet configuration error). http://fjortis.info/pub/debian/bandwidthd-latest/ Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: where do scripts go?
On Sun, Jul 11, 2004 at 01:15:55PM -0500, Steve Langasek wrote: On Sun, Jul 11, 2004 at 05:56:05AM -0700, William Ballard wrote: Where does this script belong? /usr/bin, /var/lib/package, /usr/share/package ? This is probably in the policy but I missed it. See the FHS, which is included in policy by reference. Do nonmodifiable perl scripts never intended to be directly launched by the user count as data ? My program will be called tufiler, and will have the supporting scripts demo.pl and tufiler.pl. Demo.pl will just throw up a fake file list and not actually move or rename any files, so people can get the idea of what the program does. tufiler.pl will be *my* idea of how to file scanned papers, and there's a high liklihood people will want to modify the logic. I figured people would just make a copy and specify the alternate perl script on the command line. So I can do (1) /usr/bin/tufiler-demo.pl /usr/bin/tufiler.pl (2) /etc/tufiler/tufiler.pl, /usr/share/tufiler/demo.pl (3) /usr/share/tufiler/tufiler.pl, /usr/share/tufiler/demo.pl Remember, people will never run these scripts directly. I guess maybe they belong in /etc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: where do scripts go?
William Ballard wrote: My program will be called tufiler, and will have the supporting scripts demo.pl and tufiler.pl. Demo.pl will just throw up a fake file list and not actually move or rename any files, so people can get the idea of what the program does. tufiler.pl will be *my* idea of how to file scanned papers, and there's a high liklihood people will want to modify the logic. I figured people would just make a copy and specify the alternate perl script on the command line. In that case, it's common to place the original script in /usr/share/doc/PACKAGE/examples, with instructions for the user to make a customized copy before using it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
