script-with-language-extension
Hello mentors, I have output this output from lintian: -- W: zynjacku: script-with-language-extension usr/bin/lv2rack.py W: zynjacku: script-with-language-extension usr/bin/zynjacku.py W: zynjacku: script-with-language-extension usr/bin/zynspect.py -- I tried (one by one) remove ".py" suffix, remove shebang by patch and then also change permission for these files. All these changes breaks functionality. What is right practice to solve this issue? regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
script-with-language-extension
Hi, I am in the process packaging Net::Frame::Device (libnet-frame-device-perl) as part of a the fix to a bug. Net::Frame::Device includes two scripts that are installed to /usr/bin, but both have .pl extensions therefore giving me a Lintian warning. My initial thought on fixing this is to rename the files by overriding dh_auto_install in debian/rules... but I'm struggling to find out how to do this without explicitly writing the file names, which wouldn't accommodate new files in future releases. So far I've got the following: PACKAGE = $(shell dh_listpackages) TMP = $(CURDIR)/debian/$(PACKAGE) find $(TMP)/usr/bin -name '*.pl' Which does identify the files correctly... I'm just not sure where to go from here! My second thought.. was to relocate the files to e.g /usr/share/$(PACKAGE) and then provide symlinks in /usr/bin, but this perhaps seems to more work than necessary Cheers, Daniel Lintott signature.asc Description: OpenPGP digital signature
Re: script-with-language-extension
On Mon, Oct 05, 2009 at 02:32:50AM +0200, Jaromír Mikeš wrote: > Hello mentors, > > I have output this output from lintian: > -- > W: zynjacku: script-with-language-extension usr/bin/lv2rack.py > W: zynjacku: script-with-language-extension usr/bin/zynjacku.py > W: zynjacku: script-with-language-extension usr/bin/zynspect.py > -- > > I tried (one by one) remove ".py" suffix, remove shebang by patch and then > also change permission for these files. > All these changes breaks functionality. > What is right practice to solve this issue? > don't remove the shebang, that needs to be there, and there's no reason to remove it. just remove the .py suffix. -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
Re: script-with-language-extension
From: Jose Luis Rivas JM> I have output this output from lintian: JM> -- JM> W: zynjacku: script-with-language-extension usr/bin/lv2rack.py JM> W: zynjacku: script-with-language-extension usr/bin/zynjacku.py JM> W: zynjacku: script-with-language-extension usr/bin/zynspect.py JM> -- JM> JM> I tried (one by one) remove ".py" suffix, remove shebang by patch and then also JM> change permission for these files. JM> All these changes breaks functionality. JM> What is right practice to solve this issue? JLR> Please don't remove the shebang, just the py extension :-) I did it, but it breaks functionality ... there exist also symlinks with same name and in same location. usr/bin/lv2rack usr/bin/zynjacku usr/bin/zynspect -- usr/bin/lv2rack.py usr/bin/zynjacku.py usr/bin/zynspect.py Hmmm what about remove these symlink first and then remove suffix? I am going to try it. regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
On Monday 05,October,2009 08:48 AM, Jaromír Mikeš wrote: > I did it, but it breaks functionality ... there exist also symlinks with same > name and in same location. > > usr/bin/lv2rack > usr/bin/zynjacku > usr/bin/zynspect > -- > usr/bin/lv2rack.py > usr/bin/zynjacku.py > usr/bin/zynspect.py > > Hmmm what about remove these symlink first and then remove suffix? > I am going to try it. How about just mv /usr/bin/lv2rack.py /usr/bin/lv2rack and so on? `lintian-info -t script-with-language-extension` is a good read as to why stuff in /usr/bin/ shouldn't have language extensions (.py, .pl, .sh, etc), by the way. -- Kind regards, Chow Loong Jin signature.asc Description: OpenPGP digital signature
Re: script-with-language-extension
> Od: Chow Loong Jin JM> > I did it, but it breaks functionality ... there exist also symlinks with same JM> name and in same location. JM> > usr/bin/lv2rack JM> > usr/bin/zynjacku JM> > usr/bin/zynspect JM> > -- JM> > usr/bin/lv2rack.py JM> > usr/bin/zynjacku.py JM> > usr/bin/zynspect.py > > CLJ> > Hmmm what about remove these symlink first and then remove suffix? CLJ> > I am going to try it. CLJ> How about just mv /usr/bin/lv2rack.py /usr/bin/lv2rack and so on? nice solution ... but there is anyway something broken. This package actually contains two commands you can call from CLI zynjacku and lv2rack. When I remove ".py" suffixes lv2rack stop works ... zynjacku is fine. Without removing ".py" suffixes both work fine. I have to investigate it more. regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
> Od: Jaromír Mikeš JM> > I did it, but it breaks functionality ... there exist also symlinks with JM> same name and in same location. JM> > usr/bin/lv2rack JM> > usr/bin/zynjacku JM> > usr/bin/zynspect JM> > -- JM> > usr/bin/lv2rack.py JM> > usr/bin/zynjacku.py JM> > usr/bin/zynspect.py CLJ> > Hmmm what about remove these symlink first and then remove suffix? CLJ> > I am going to try it. CLJ> How about just mv /usr/bin/lv2rack.py /usr/bin/lv2rack and so on? JM> nice solution ... but there is anyway something broken. JM> This package actually contains two commands you can call from CLI zynjacku and JM> lv2rack. JM> When I remove ".py" suffixes lv2rack stop works ... zynjacku is fine. JM> Without removing ".py" suffixes both work fine. JM> I have to investigate it more. BTW: error message for lv2rack is: --- $ lv2rack Traceback (most recent call last): File "/usr/bin/lv2rack", line 52, in import zynjacku as zynjacku -- I got warning from other mailing list that this package ships a python module but it is not compatible with the python policy. I hope that I solved it but using python-support. Not sure if these two thing are connected. regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
On Monday 05,October,2009 09:43 AM, Jaromír Mikeš wrote: > BTW: error message for lv2rack is: > --- > $ lv2rack > Traceback (most recent call last): > File "/usr/bin/lv2rack", line 52, in > import zynjacku as zynjacku > -- > > I got warning from other mailing list that this package ships a python module > but it is not compatible > with the python policy. I hope that I solved it but using python-support. > Not sure if these two thing are connected. > > regards > > mira > > You should probably try reading the Debian Python New Policy[1] and getting help from #debian-python on OFTC or debian-pyt...@lists.debian.org. [1] http://wiki.debian.org/DebianPython/NewPolicy -- Kind regards, Chow Loong Jin signature.asc Description: OpenPGP digital signature
Re: script-with-language-extension
On Mon, Oct 05, 2009 at 03:43:22AM +0200, Jarom?r Mike? wrote: > > Od: Jarom?r Mike? > > JM> > I did it, but it breaks functionality ... there exist also symlinks with > JM> same name and in same location. > > JM> > usr/bin/lv2rack > JM> > usr/bin/zynjacku > JM> > usr/bin/zynspect > JM> > -- > JM> > usr/bin/lv2rack.py > JM> > usr/bin/zynjacku.py > JM> > usr/bin/zynspect.py > > CLJ> > Hmmm what about remove these symlink first and then remove suffix? > CLJ> > I am going to try it. > CLJ> How about just mv /usr/bin/lv2rack.py /usr/bin/lv2rack and so on? > > JM> nice solution ... but there is anyway something broken. > JM> This package actually contains two commands you can call from CLI > zynjacku and > JM> lv2rack. > JM> When I remove ".py" suffixes lv2rack stop works ... zynjacku is fine. > JM> Without removing ".py" suffixes both work fine. > JM> I have to investigate it more. > > BTW: error message for lv2rack is: > --- > $ lv2rack > Traceback (most recent call last): > File "/usr/bin/lv2rack", line 52, in > import zynjacku as zynjacku > -- So someone's using a single file as both a library and a stand-alone program. Damned silly idea. Stick zynjacku.py in a proper library path somewhere, and write a little shim wrapper to stick in /usr/bin that calls zynjacku as it expects to be called. - Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
> Od: Chow Loong Jin > You should probably try reading the Debian Python New Policy[1] and getting > help > from #debian-python on OFTC or debian-pyt...@lists.debian.org. > > [1] http://wiki.debian.org/DebianPython/NewPolicy I didn't know that there is debian-python list, I will try ask there. Thank you for help. regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
> Od: Matthew Palmer JM> > I did it, but it breaks functionality ... there exist also symlinks JM> > with same name and in same location. JM> > usr/bin/lv2rack JM> > usr/bin/zynjacku JM> > usr/bin/zynspect JM> > -- JM> > usr/bin/lv2rack.py JM> > usr/bin/zynjacku.py JM> > usr/bin/zynspect.py CLJ> > Hmmm what about remove these symlink first and then remove suffix? CLJ> > I am going to try it. CLJ> How about just mv /usr/bin/lv2rack.py /usr/bin/lv2rack and so on? JM> nice solution ... but there is anyway something broken. JM> This package actually contains two commands you can call from CLI zynjacku JM> and lv2rack. JM> When I remove ".py" suffixes lv2rack stop works ... zynjacku is fine. JM> Without removing ".py" suffixes both work fine. JM> I have to investigate it more. JM> > BTW: error message for lv2rack is: JM> > --- JM> > $ lv2rack JM> > Traceback (most recent call last): JM> > File "/usr/bin/lv2rack", line 52, in JM> > import zynjacku as zynjacku JM> > -- MP> So someone's using a single file as both a library and a stand-alone MP> program. Damned silly idea. Stick zynjacku.py in a proper library path MP> somewhere, and write a little shim wrapper to stick in /usr/bin that calls MP> zynjacku as it expects to be called. Do you know any package using "shim wrapper"? It would be good starting point for learning this method. regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
Matthew Palmer writes: > So someone's using a single file as both a library and a stand-alone > program. Damned silly idea. Not so silly; a Python module can be useful both as a main program and as a re-useable component in other programs. The well-known Python idiom of testing ‘if __name__ == '__main__'’ is commonly used to make a module that can be used in either way. > Stick zynjacku.py in a proper library path somewhere, and write a > little shim wrapper to stick in /usr/bin that calls zynjacku as it > expects to be called. Yes, that's one way to do it, and quite valid. It does, though, involve creating that shim separately after installing the distribution. IIUC, the ‘entry_points’ facility (of the third-party ‘pkg_resources’ module) is another way, that allows the program file to be created automatically, such that when run it will invoke a specified function, along with the rest of the distribution's installation process. -- \ “I'm a great lover, I'll bet.” —Emo Philips | `\ | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
> Od: Ben Finney MP> > Stick zynjacku.py in a proper library path somewhere, and write a MP> > little shim wrapper to stick in /usr/bin that calls zynjacku as it MP> > expects to be called. BF> Yes, that's one way to do it, and quite valid. It does, though, involve BF> creating that shim separately after installing the distribution. BF> IIUC, the ‘entry_points’ facility (of the third-party ‘pkg_resources’ BF> module) is another way, that allows the program file to be created BF> automatically, such that when run it will invoke a specified function, BF> along with the rest of the distribution's installation process. Any link where I can study more to understand and solve problem? regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
Jaromír Mikeš writes: > Any link where I can study more to understand and solve problem? The ‘debian-python’ forum already mentioned, and the documentation (such as it is) for the popular third-party ‘setuptools’ extension for the Python distutils. -- \ “I think it would be a good idea.” —Mahatma Gandhi (when asked | `\ what he thought of Western civilization) | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
On Mon, 2009-10-05 at 13:12 +1100, Matthew Palmer wrote: > On Mon, Oct 05, 2009 at 03:43:22AM +0200, Jarom?r Mike? wrote: > > > Od: Jarom?r Mike? > > > > JM> > I did it, but it breaks functionality ... there exist also symlinks > > with > > JM> same name and in same location. > > > > JM> > usr/bin/lv2rack > > JM> > usr/bin/zynjacku > > JM> > usr/bin/zynspect > > JM> > -- > > JM> > usr/bin/lv2rack.py > > JM> > usr/bin/zynjacku.py > > JM> > usr/bin/zynspect.py > > > > CLJ> > Hmmm what about remove these symlink first and then remove suffix? > > CLJ> > I am going to try it. > > CLJ> How about just mv /usr/bin/lv2rack.py /usr/bin/lv2rack and so on? > > > > JM> nice solution ... but there is anyway something broken. > > JM> This package actually contains two commands you can call from CLI > > zynjacku and > > JM> lv2rack. > > JM> When I remove ".py" suffixes lv2rack stop works ... zynjacku is fine. > > JM> Without removing ".py" suffixes both work fine. > > JM> I have to investigate it more. > > > > BTW: error message for lv2rack is: > > --- > > $ lv2rack > > Traceback (most recent call last): > > File "/usr/bin/lv2rack", line 52, in > > import zynjacku as zynjacku > > -- > > So someone's using a single file as both a library and a stand-alone > program. Damned silly idea. Stick zynjacku.py in a proper library path > somewhere, and write a little shim wrapper to stick in /usr/bin that calls > zynjacku as it expects to be called. Involving upstream is always a good idea in these cases, since you will be creating a divergence from pristine upstream source. Also, isn't it possible to install zynjacku.py in site-packages (before calling dh_pysupport, of course) and symlinking it from /usr/bin possible too? -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
On Mon, Oct 05, 2009 at 01:44:11PM +1100, Ben Finney wrote: > Matthew Palmer writes: > > > So someone's using a single file as both a library and a stand-alone > > program. Damned silly idea. > > Not so silly; a Python module can be useful both as a main program and > as a re-useable component in other programs. The well-known Python idiom > of testing ???if __name__ == '__main__'??? is commonly used to make a module > that can be used in either way. It can be done in other languages too; doesn't make it a good idea. - Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
Le Mon, Oct 05, 2009 at 02:32:50AM +0200, Jaromír Mikeš a écrit : > Hello mentors, > > I have output this output from lintian: > -- > W: zynjacku: script-with-language-extension usr/bin/lv2rack.py > W: zynjacku: script-with-language-extension usr/bin/zynjacku.py > W: zynjacku: script-with-language-extension usr/bin/zynspect.py > -- Dear Jaromír, for reason that I explained on debian-devel, I think that in that case it is an error to modify program names. This creates difficulties for our users who collaborate with users of other operating systems, for a benefit that is in my opinion very hypothetical in most cases. http://lists.debian.org/msgid-search/20091001012838.ga30...@kunpuu.plessy.org I have repened the Policy bug where the renaming policy was decided, and hope to get it reverted. http://bugs.debian.org/190753 Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
On 2009-10-05, Charles Plessy wrote: > I have repened the Policy bug where the renaming policy was decided, and hope > to get it reverted. Don't expect it to happen, but you are free to hope. /Sune -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
> Od: Charles Plessy > JM> > I have output this output from lintian: JM> > -- JM> > W: zynjacku: script-with-language-extension usr/bin/lv2rack.py JM> > W: zynjacku: script-with-language-extension usr/bin/zynjacku.py JM> > W: zynjacku: script-with-language-extension usr/bin/zynspect.py JM> > -- CP> for reason that I explained on debian-devel, I think that in that case it is an CP> error to modify program names. This creates difficulties for our users who CP> collaborate with users of other operating systems, for a benefit that is in my CP> opinion very hypothetical in most cases. CP> http://lists.debian.org/msgid-search/20091001012838.ga30...@kunpuu.plessy.org CP> I have repened the Policy bug where the renaming policy was decided, and hope CP> to get it reverted. CP> http://bugs.debian.org/190753 Hello Charles, thanks for you answer. I red with interest you suggestions and your argument seems to be very reasonable for me. I hope it will end in some improvement in debian policy. This renaming practices make things really confusing, but I am not experienced enough to be sure what solution is best. Anyway at least "Debian universal best practices" paper would be great. I just thinking what I will write to upstream, how I will describe problem and what I will want to be changed or improved from him. To have this things clear would be great. Such paper would save a lot of resources. best regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: script-with-language-extension
Not sure if fixing it by renaming the files is what you want to do. I have such a warning in xinetd and honestly I just ignore it because I don't think that renaming scripts after they have been there for many years is a good idea. Besides that's the upstream name so that's how they will be probably called in other distributions too I guess. In data domenica 9 marzo 2014 19:52:04, Daniel Lintott ha scritto: > Hi, > > I am in the process packaging Net::Frame::Device > (libnet-frame-device-perl) as part of a the fix to a bug. > > Net::Frame::Device includes two scripts that are installed to /usr/bin, > but both have .pl extensions therefore giving me a Lintian warning. > > My initial thought on fixing this is to rename the files by overriding > dh_auto_install in debian/rules... but I'm struggling to find out how to > do this without explicitly writing the file names, which wouldn't > accommodate new files in future releases. > > So far I've got the following: > > PACKAGE = $(shell dh_listpackages) > TMP = $(CURDIR)/debian/$(PACKAGE) > > > find $(TMP)/usr/bin -name '*.pl' > > Which does identify the files correctly... I'm just not sure where to go > from here! > > My second thought.. was to relocate the files to e.g > /usr/share/$(PACKAGE) and then provide symlinks in /usr/bin, but this > perhaps seems to more work than necessary > > Cheers, > Daniel Lintott -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galileo Galilei http://ltworf.github.io/ltworf/ signature.asc Description: This is a digitally signed message part.
Re: script-with-language-extension
On 9 Mar 2014 19:52, "Daniel Lintott" wrote:
>
> Hi,
>
> I am in the process packaging Net::Frame::Device
> (libnet-frame-device-perl) as part of a the fix to a bug.
>
> Net::Frame::Device includes two scripts that are installed to /usr/bin,
> but both have .pl extensions therefore giving me a Lintian warning.
>
> My initial thought on fixing this is to rename the files by overriding
> dh_auto_install in debian/rules... but I'm struggling to find out how to
> do this without explicitly writing the file names, which wouldn't
> accommodate new files in future releases.
>
> So far I've got the following:
>
> PACKAGE = $(shell dh_listpackages)
> TMP = $(CURDIR)/debian/$(PACKAGE)
>
>
> find $(TMP)/usr/bin -name '*.pl'
>
> Which does identify the files correctly... I'm just not sure where to go
> from here!
How about:
find $(TMP)/usr/bin -name "*.pl" -exec rename 's/\.pl$//' {} +
Just make sure you do it at build time, not install time.
Will be interesting to hear others thoughts.
HTH
--
Kind Regards,
Dave Walker
Re: script-with-language-extension
On Sun, 09 Mar 2014 21:39:01 +, Dave Walker wrote:
> > Net::Frame::Device includes two scripts that are installed to /usr/bin,
> > but both have .pl extensions therefore giving me a Lintian warning.
> >
> > My initial thought on fixing this is to rename the files by overriding
> > dh_auto_install in debian/rules... but I'm struggling to find out how to
> > do this without explicitly writing the file names, which wouldn't
> > accommodate new files in future releases.
> >
> > So far I've got the following:
> >
> > PACKAGE = $(shell dh_listpackages)
> > TMP = $(CURDIR)/debian/$(PACKAGE)
> >
> >
> > find $(TMP)/usr/bin -name '*.pl'
> >
> How about:
> find $(TMP)/usr/bin -name "*.pl" -exec rename 's/\.pl$//' {} +
> Just make sure you do it at build time, not install time.
Looks good, and similar to existing examples which might be a bit simpler:
libdata-stag-perl/debian/rules: prename 's/\.pl//' $(TMP)/usr/bin/*
libdata-stag-perl/debian/rules: prename 's/\.pl//'
$(TMP)/usr/share/man/man1/*1p*
libdbix-dbstag-perl/debian/rules: rename 's/\.pl//'
debian/libdbix-dbstag-perl/usr/share/man/man1/*.pl.1p
libdbix-dbstag-perl/debian/rules: rename 's/\.pl//'
debian/libdbix-dbstag-perl/usr/bin/*.pl
libembperl-perl/debian/rules: rename -v 's/\.pl//' $(TMP)/usr/bin/emb*
libembperl-perl/debian/rules: rename -v 's/\.pl//'
$(TMP)/usr/share/man/man1/emb*
libgeo-osm-tiles-perl/debian/rules: prename 's/\.pl$$//'
$(TMP)/usr/bin/downloadosmtiles.pl
libgeo-osm-tiles-perl/debian/rules: prename 's/\.pl\.1p$$/.1p/'
$(TMP)/usr/share/man/man1/downloadosmtiles.pl.1p
libtext-ngrams-perl/debian/rules: rename -v 's/\.pl//' $(TMP)/usr/bin/*.pl
libtext-ngrams-perl/debian/rules: rename -v 's/\.pl//'
$(TMP)/usr/share/man/man1/*
libvm-ec2-perl/debian/rules:rename 's/\.pl//' $(TMP)/usr/bin/*.pl
libvm-ec2-perl/debian/rules:rename 's/\.pl//' $(TMP)/usr/share/man/man1/*
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Aerzte: Männer sind Schweine
signature.asc
Description: Digital Signature
Re: script-with-language-extension
On 03/10/2014 04:49 AM, Salvo Tomaselli wrote: > Not sure if fixing it by renaming the files is what you want to do. > > I have such a warning in xinetd and honestly I just ignore it because I don't > think that renaming scripts after they have been there for many years is a > good idea. Besides that's the upstream name so that's how they will be > probably called in other distributions too I guess. The Debian policy manual don't agree with you, AFAIR. Thomas -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/531d6797.7000...@debian.org
Re: script-with-language-extension
Le Mon, Mar 10, 2014 at 03:19:51PM +0800, Thomas Goirand a écrit : > On 03/10/2014 04:49 AM, Salvo Tomaselli wrote: > > Not sure if fixing it by renaming the files is what you want to do. > > > > I have such a warning in xinetd and honestly I just ignore it because I > > don't > > think that renaming scripts after they have been there for many years is a > > good idea. Besides that's the upstream name so that's how they will be > > probably called in other distributions too I guess. > > The Debian policy manual don't agree with you, AFAIR. Hi Thomas, This is very unfortunate. I have ashamed myself sending scripts to colleagues that did not work on their platform, just because I developed them on Debian, which "corrects" file names unilaterally. I would prefer my colleagues to know Debian for being rock solid and secure, rather than know it for being incompatible by design with the rest of the Unix world. Cheers, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140310072711.gc9...@falafel.plessy.net
Re: script-with-language-extension
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/14 00:26, gregor herrmann wrote:
> On Sun, 09 Mar 2014 21:39:01 +, Dave Walker wrote:
>
>>> Net::Frame::Device includes two scripts that are installed to
>>> /usr/bin, but both have .pl extensions therefore giving me a
>>> Lintian warning.
>>>
>>> My initial thought on fixing this is to rename the files by
>>> overriding dh_auto_install in debian/rules... but I'm
>>> struggling to find out how to do this without explicitly
>>> writing the file names, which wouldn't accommodate new files in
>>> future releases.
>>>
>>> So far I've got the following:
>>>
>>> PACKAGE = $(shell dh_listpackages) TMP =
>>> $(CURDIR)/debian/$(PACKAGE)
>>>
>>> find $(TMP)/usr/bin -name '*.pl'
>>>
>
>> How about: find $(TMP)/usr/bin -name "*.pl" -exec rename
>> 's/\.pl$//' {} + Just make sure you do it at build time, not
>> install time.
>
> Looks good, and similar to existing examples which might be a bit
> simpler:
>
> libvm-ec2-perl/debian/rules:rename 's/\.pl//'
> $(TMP)/usr/bin/*.pl libvm-ec2-perl/debian/rules:rename
> 's/\.pl//' $(TMP)/usr/share/man/man1/*
>
I knew I'd seen it somewhere, but for the life of me couldn't remember
which package it was in!
Thanks, for the help guys!
Cheers,
Daniel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBAgAGBQJTHZYLAAoJEMhyZNddc+xuhEwP/jgRWFFqTBJH7+Ss0RGL+x/k
o0r3vbxiOn1KDdtk4cQ3goYiAAuycKwphtZ2VOv1ovkUlMOM1fRtkKfAkYkLOE8+
9BxKvbYS2myHfeIoeT52koKob2xhXv7IJRxywlJTRmgtTgDQaq002K23zY1+Umap
XOo/A0Ek8iDlIfcr26v6ygm5AD7sPucMcCvHCwM5N7rchAFR//1rg1Pyi8r32COS
9OCXCsvU5/KDwnRJlZODpZbbBq3kLVLrOjuD7OA8fm0i3+ibM7+pNloQegAa0/UM
RKtoUL20b4A8tQA3tJG+3CHWzuTMOgbKgn0K234x08aSr7wtvUxQhJReUrNgCveL
j9WY3MN1fPOojjttH/RrrZ29IjhYCLwxBMZrsLR7kiSFQZUo0dQb6XN+JhrDXhXd
rNZlmXuKIW0tLENXCZPLWCVnStsO1/xC1hc1164Y12qlKAAiwLJRqJJG6qiU1H14
/HafDbGDKlZA6oEcEYh1s6fTSzC/tsCETjsJHByh9TBqkuaw/5jqk1Ee+LUOBqPJ
2J17GjKgqQYge7WEmN35rdnHIjvIzVxTRejlTsRzUmKHuxoscwIkY7GOy/8jV++G
dVyvO6A14Iq63ngEToJ5R/nfotRNvTHsVgnWqMFbi8FcpP/R8S6vWIKo3KTzPFLy
3l7d7HiQHfKeljLXdNG2
=MYWT
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/531d9614.5030...@serverb.co.uk
Re: script-with-language-extension
> > The Debian policy manual don't agree with you, AFAIR. I know it doesn't, that's why lintian complains. But what should I do? I think renaming a command would cause more disruption. Best -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galileo Galilei http://ltworf.github.io/ltworf/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2722325.GjvIDOAIiL@vulcano
