27 Aug
2009
27 Aug
'09
8:52 a.m.
On Wed, 26 Aug 2009 23:42:12 +0200
Fons Adriaensen <fons(a)kokkinizita.net> wrote:
ciao,
Renato
On Wed, Aug 26, 2009 at 11:09:27PM +0200, Renato
wrote:
Well, I don't know about LADSPA plugins, but the fact is that in Arch
for building from source in a pacman-aware (pacman is Arch's package
manager) manner, you need the DESTDIR option... infact you first
install all the files with the exact same direcotry tree as would
do 'make install' but, instead of in root, in a working directory...
i.e. you do
'make DESTDIR=/pathtotmpdir install'
Then you point pacman to /pathtotmpdir, so he knows what to install and
where on the system and keeps neatly track of it (you can then easily
remove the package).
So for Archers the DESTDIR is important, but on the other hand it's
easy to patch a Makefile if it doesn't have the DESTDIR option, so no
real big problem for now... just a heads up for the future.
Hello, I've packaged this plugin for
Archlinux, it's now in the AUR
Thanks ! It's a bit unfortunate you acted so quickly - the plugin
is still in a 'beta' stage and following releases could well be
incompatible. This is no big deal for people who install from
source, but could generate some trouble for the others.
btw it would be good if in 'make install'
the necessary files are
copied to $(DESTDIR)/pathtowherecopyfiles rather than
simply /pathtowherecopyfiles ; this surely makes packaging much
easier on Arch
How should this be split up ? AFAIK there's only one place to
install LADPSA plugins, and the usual /usr or /usr/local
separation is not used. But I could be wrong about this.
and also btw,
good plugin - I've used it with good results with the
settings suggested by Gabriel :)
Fine !
Ciao,
27 Aug
27 Aug
9:04 a.m.
New subject: Auto-wah plugin
On Thu, 27 Aug 2009 12:55:36 +0200
Renato <rennabh(a)gmail.com> wrote:
On Wed, 26 Aug 2009 23:42:12 +0200
Fons Adriaensen <fons(a)kokkinizita.net> wrote:
ciao,
Renato
Hi Fons.
On Arch we use scripts to easily build packages from source and install
those. The files get installed into a fakeroot environment, then it
gets packaged. The DESTDIR variable points to the fakeroot.
I patched a number of your applications makefiles to include DESTDIR
but it would of course be more convenient if we wouldn't have to do so.
I guess other package management systems use fakeroot as well and would
also benefit.
Regards,
Philipp
On Wed, Aug 26, 2009 at 11:09:27PM +0200, Renato
wrote:
Well, I don't know about LADSPA plugins, but the fact is that in Arch
for building from source in a pacman-aware (pacman is Arch's package
manager) manner, you need the DESTDIR option... infact you first
install all the files with the exact same direcotry tree as would
do 'make install' but, instead of in root, in a working directory...
i.e. you do
'make DESTDIR=/pathtotmpdir install'
Then you point pacman to /pathtotmpdir, so he knows what to install
and where on the system and keeps neatly track of it (you can then
easily remove the package).
So for Archers the DESTDIR is important, but on the other hand it's
easy to patch a Makefile if it doesn't have the DESTDIR option, so no
real big problem for now... just a heads up for the future.
Hello, I've packaged this plugin for
Archlinux, it's now in the
AUR
Thanks ! It's a bit unfortunate you acted so quickly - the plugin
is still in a 'beta' stage and following releases could well be
incompatible. This is no big deal for people who install from
source, but could generate some trouble for the others.
btw it would be good if in 'make install'
the necessary files are
copied to $(DESTDIR)/pathtowherecopyfiles rather than
simply /pathtowherecopyfiles ; this surely makes packaging much
easier on Arch
How should this be split up ? AFAIK there's only one place to
install LADPSA plugins, and the usual /usr or /usr/local
separation is not used. But I could be wrong about this.
and also
btw, good plugin - I've used it with good results with
the settings suggested by Gabriel :)
Fine !
Ciao,
9:50 a.m.
New subject: Auto-wah plugin
On Thu, 27 Aug 2009 13:04:13 +0200
<hollunder(a)gmx.at> wrote:
On Thu, 27 Aug 2009 12:55:36 +0200
Renato <rennabh(a)gmail.com> wrote:
Since I'm working on this, just one more thing: it would be great if
the tar.bz2 and the package in general would be called wah-plugins
instead of WAH-plugins; Arch doesn't support capital letters in
package's names, so I had to call it wah-plugins but then the
incosistency brings up some more (little) issues in packaging.
Renato
On Wed, 26 Aug 2009 23:42:12 +0200
Fons Adriaensen <fons(a)kokkinizita.net> wrote:
ciao,
Renato
Hi Fons.
On Arch we use scripts to easily build packages from source and
install those. The files get installed into a fakeroot environment,
then it gets packaged. The DESTDIR variable points to the fakeroot.
I patched a number of your applications makefiles to include DESTDIR
but it would of course be more convenient if we wouldn't have to do
so. I guess other package management systems use fakeroot as well and
would also benefit.
Regards,
Philipp
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev On Wed, Aug 26, 2009 at 11:09:27PM +0200, Renato
wrote:
Well, I don't know about LADSPA plugins, but the fact is that in
Arch for building from source in a pacman-aware (pacman is Arch's
package manager) manner, you need the DESTDIR option... infact you
first install all the files with the exact same direcotry tree as
would do 'make install' but, instead of in root, in a working
directory... i.e. you do
'make DESTDIR=/pathtotmpdir install'
Then you point pacman to /pathtotmpdir, so he knows what to install
and where on the system and keeps neatly track of it (you can then
easily remove the package).
So for Archers the DESTDIR is important, but on the other hand it's
easy to patch a Makefile if it doesn't have the DESTDIR option, so
no real big problem for now... just a heads up for the future.
Hello, I've packaged this plugin for
Archlinux, it's now in the
AUR
Thanks ! It's a bit unfortunate you acted so quickly - the plugin
is still in a 'beta' stage and following releases could well be
incompatible. This is no big deal for people who install from
source, but could generate some trouble for the others.
btw it would be good if in 'make install'
the necessary files
are copied to $(DESTDIR)/pathtowherecopyfiles rather than
simply /pathtowherecopyfiles ; this surely makes packaging much
easier on Arch
How should this be split up ? AFAIK there's only one place to
install LADPSA plugins, and the usual /usr or /usr/local
separation is not used. But I could be wrong about this.
and also
btw, good plugin - I've used it with good results with
the settings suggested by Gabriel :)
Fine !
Ciao,
6:11 p.m.
New subject: Auto-wah plugin
On Thu, Aug 27, 2009 at 01:04:13PM +0200, hollunder(a)gmx.at wrote:
Hi Fons.
On Arch we use scripts to easily build packages from source and install
those. The files get installed into a fakeroot environment, then it
gets packaged. The DESTDIR variable points to the fakeroot.
I patched a number of your applications makefiles to include DESTDIR
but it would of course be more convenient if we wouldn't have to do so.
I guess other package management systems use fakeroot as well and would
also benefit.
I'll try to make life easy for packagers, but I can't promise
to accomodate all their wishes... For two reasons, first these
requirements may be conflicting, second I'm somewhat reluctant
to put things in e.g. Makefiles that I can't routinely test myself.
My primary concern for Makefiles is to ensure that an installation
from source works as expected. Which means using installation paths
based on $(PREFIX) taking into account 64-bit, etc. Your $(DESTDIR)
wants to override all of these, it's not very clear to me how to do
this.
There are also apps that will install into different places, e.g.
jkmeters installs a binary in $(PREFIX)/bin and some png files in
$(PREFIX)/share/jkmeters.
And to complicate things, the next release of TetraProc will use
$(PREFIX)/share/jkmeters as well, as it installs a subset of the
same png files, and I want them to be shared between all apps that
use them (and that number is bound to increase).
How would you handle this ?
Regarding the use of upper case, Unix and Linux do have case-sensitive
filenames. Any packaging system that tries to ignore that does so at
its own risk.
Ciao,
--
FA
Io lo dico sempre: l'Italia è troppo stretta e lunga.
6:37 p.m.
New subject: Auto-wah plugin
Am Thu, 27. Aug 2009 um 22:10:59 +0200 schrieb Fons Adriaensen:
Hi Fons,
There are also apps that will install into different
places, e.g.
jkmeters installs a binary in $(PREFIX)/bin and some png files in
$(PREFIX)/share/jkmeters.
And to complicate things, the next release of TetraProc will use
$(PREFIX)/share/jkmeters as well, as it installs a subset of the
same png files, and I want them to be shared between all apps that
use them (and that number is bound to increase).
How would you handle this ?
this is quite easy, the install target goes always to
$DESTDIR$PREFIX/somepath
where $PREFIX is commonly "/usr" or "/usr/local" or sometimes
"/opt".
The need for "$DESTDIR" is common to all kind of packaging tools,
because during package build they will install the complete file set to
a temporary path (=DESTDIR) and then wrap it all up.
If you would have a look to a Makefile written by automake/autoconf you
could see (and understand) in detail how it is used (even in a much more
complex setup).
Guido
--
http://www.bayernline.de/~gscholz/
http://www.lug-burghausen.org/
5366
days inactive
5366
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Fons Adriaensen -
Guido Scholz -
hollunder＠gmx.at -
Renato