[PD-dev] pd-extended exectuable - packaging for Debian

Hans-Christoph Steiner hans at at.or.at
Tue Aug 13 23:39:55 CEST 2013


On 08/12/2013 08:59 PM, zmoelnig at iem.at wrote:
> 
> Quoting Kaj Ailomaa <zequence at mousike.me>:
>> I solve it by using a postinst script to rename the two files that
>> shouldn't.
> 
> this is most likely the wrong approach.
> 
> 
> "postinst" is running on the target system, so instead of renaming the file
> *once* during the build process, you will rename it thousands of times (on
> each installation).
> this also means that you double your chance of creating package collision and
> circumvent any security measures of the package manager (e.g. apt keeps track
> of the installed files - but it defers that information from the list of files
> in the .deb rather than checking which files have been installed after running
> postinst)


Ideally, the pd-extended build system would name the executable properly, but
it currently does the wrong thing.  For the packaging, I think the best thing
to do right now is to use a debian/install file to install the file as
usr/bin/pd-extended.  I think the line in debian/install would look like this:

usr/bin/pd  usr/bin/pd-extended

As for basing the pd-extended package off of the 'puredata' package, I think
that is not a good idea.  The pd-extended package will generate a single
package called pd-extended.  The puredata package generates lots of sub
packages which don't make sense for Pd-extended.  Also, Pd-extended's build
system (./configure, etc.) is not the same as pd-vanilla's.

.hc



More information about the Pd-dev mailing list