can-utils: install in /usr/bin instead of /usr/local/bin ??
Hi Marc,
when can-utils are now intended to be packaged for Debian:
Does it make sense to move the installation directory to /usr/bin instead of the current /usr/local/bin target??
Regards,
Oliver
Marc Kleine-Budde
maintainerQuoted 6 lines · Oliver Hartkopp
Hi Marc,
when can-utils are now intended to be packaged for Debian:
Does it make sense to move the installation directory to
/usr/bininstead of the current/usr/local/bintarget??
No, Uwe will probably use ./configure --prefix=/usr
Marc
Signature · 4 lines
Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
Quoted 9 lines · Marc Kleine-Budde
Quoted 6 lines · Oliver Hartkopp
Hi Marc,
when can-utils are now intended to be packaged for Debian:
Does it make sense to move the installation directory to
/usr/bininstead of the current/usr/local/bintarget??No, Uwe will probably use ./configure --prefix=/usr
CC Alexander and Nikita.
Yegor
Marc Kleine-Budde
maintainerQuoted 4 lines · Yegor Yefremov
Quoted 3 lines · Marc Kleine-Budde
Quoted 2 lines · Oliver Hartkopp
Hi Marc,
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
when can-utils are now intended to be packaged for Debian:
Does it make sense to move the installation directory to
/usr/bininstead of the current/usr/local/bintarget??No, Uwe will probably use ./configure --prefix=/usr
CC Alexander and Nikita.
I consider the plain Makefile legacy, so using autotools for the debian package is the way to go. The standard way to configure the installation prefix is: ./configure --prefix=/usr
Marc
Signature · 4 lines
Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
Thu, 23 Jan 2014 15:12:07 +0100
Quoted 11 lines · Marc Kleine-Budde
Quoted 10 lines · Yegor Yefremov
Quoted 8 lines · Marc Kleine-Budde
Quoted 6 lines · Oliver Hartkopp
Hi Marc,
when can-utils are now intended to be packaged for Debian:
Does it make sense to move the installation directory to
/usr/bininstead of the current/usr/local/bintarget??
Quoted 7 lines
Quoted 3 lines
Quoted 1 line
No, Uwe will probably use ./configure --prefix=/usr
CC Alexander and Nikita.
I consider the plain
Makefilelegacy, so using autotools for the debian package is the way to go. The standard way to configure the installation prefix is: ./configure --prefix=/usr
Well... I seen some strange behavior when tried to use autohell So I use plain Makefile in my not-yet-uploaded-into-Debian package.
If you want to get rid of it, I'd recommend you remove it completely from git, rename auto* to common name (for now Makefile called GNUmakefile or something like that) and remove from git any autogenerated files.
So can I do auto*/configure/make, than make distclean and there will be no *changed* files (if there are any *new* files - it's Ok).
Otherwise package maintainers have some headache in writing correct build scripts.
Signature · 1 line
Regards, Alexander.
Marc Kleine-Budde
maintainerQuoted 16 lines · Alexander GQ Gerasiov
Thu, 23 Jan 2014 15:12:07 +0100
Quoted 13 lines · Marc Kleine-Budde
Quoted 12 lines · Yegor Yefremov
Quoted 9 lines · Marc Kleine-Budde
Quoted 6 lines · Oliver Hartkopp
Hi Marc,
when can-utils are now intended to be packaged for Debian:
Does it make sense to move the installation directory to
/usr/bininstead of the current/usr/local/bintarget??No, Uwe will probably use ./configure --prefix=/usr
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
CC Alexander and Nikita.
I consider the plain
Makefilelegacy, so using autotools for the debian package is the way to go. The standard way to configure the installation prefix is: ./configure --prefix=/usrWell... I seen some strange behavior when tried to use autohell
What kind of strange behaviour?
Quoted 6 lines
So I use plain
Makefilein my not-yet-uploaded-into-Debian package.If you want to get rid of it, I'd recommend you remove it completely from git, rename auto* to common name (for now
Makefilecalled GNUmakefile or something like that) and remove from git any autogenerated files.
From the GNU make info page:
""By default, when make' looks for the makefile, it tries the following names, in order: GNUmakefile', makefile' and Makefile'.""
So GNUmakefile has a higher priority as Makefile.
There aren't any auto generated files in the git.
Quoted 2 lines
So can I do auto*/configure/make, than make distclean and there will be no *changed* files (if there are any *new* files - it's Ok).
Just call:
./autogen.sh
./configure
make
Should work out of the box.
Quoted 2 lines
Otherwise package maintainers have some headache in writing correct build scripts.
Marc
Signature · 4 lines
Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
Marc Kleine-Budde
maintainerQuoted 27 lines · Alexander GQ Gerasiov
Thu, 23 Jan 2014 21:32:58 +0100
Quoted 7 lines · Marc Kleine-Budde
Quoted 6 lines
So I use plain
Makefilein my not-yet-uploaded-into-Debian package.If you want to get rid of it, I'd recommend you remove it completely from git, rename auto* to common name (for now
Makefilecalled GNUmakefile or something like that) and remove from git any autogenerated files.Quoted 5 lines
From the GNU make info page:
""By default, whenmake' looks for the makefile, it tries the following names, in order:GNUmakefile',makefile' andMakefile'.""So GNUmakefile has a higher priority as
Makefile.Oh, didn't knew that. Ok.
Quoted 1 line
There aren't any auto generated files in the git.
Really strange, just tried to reproduce this and didn't find any problems. May be I confuse can-utils with another code, I packaged on the holiday, dont know =\
Quoted 5 lines
Just call:
./autogen.sh
./configure
make
Quoted 7 lines
In my case there will be just
#!/usr/bin/make -f
%:dh $@ --with autoreconfin debian/rules :)
Nice, just contact me here on this mailinglist if you encounter any problems.
Marc
Signature · 4 lines
Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
Thu, 23 Jan 2014 21:32:58 +0100
Quoted 7 lines · Marc Kleine-Budde
Quoted 6 lines
So I use plain
Makefilein my not-yet-uploaded-into-Debian package.If you want to get rid of it, I'd recommend you remove it completely from git, rename auto* to common name (for now
Makefilecalled GNUmakefile or something like that) and remove from git any autogenerated files.
Quoted 5 lines
From the GNU make info page:
""By default, whenmake' looks for the makefile, it tries the following names, in order:GNUmakefile',makefile' andMakefile'.""So GNUmakefile has a higher priority as
Makefile.
Oh, didn't knew that. Ok.
Quoted 1 line
There aren't any auto generated files in the git.
Really strange, just tried to reproduce this and didn't find any problems. May be I confuse can-utils with another code, I packaged on the holiday, dont know =\
Quoted 5 lines
Just call:
./autogen.sh
./configure
make
In my case there will be just
#!/usr/bin/make -f
%:
dh $@ --with autoreconf
in debian/rules :)