On May 17, 2009, at 12:36 PM, Timur Batyrshin wrote:
В Sat, 16 May 2009 19:40:31 -0400
Hans-Christoph Steiner <h...@at.or.at> пишет:
Basically, libraries/externals can't be installed into 'pd/extra'
because then the packages would conflict. I proposed /usr/lib/pd-
externals/ as a place to install all packaged externals, so then you
could have pd-vanilla, pd-extended, desiredata, etc. installed and
they could all use the externals. Claude of pure-dyne had an
objection to this, but he didn't follow up on the details.
Is there a problem with standalone externals or what? If the
prepackaged externals should only be linked with the "parent" Pd
version then you could use %_libdir/%name/extra for such and
%_libdir/pd-externals/ for the standalone
See my previous email in this thread.
In any case, I think we should discuss it here so we can work out a
common solution.
Actually, here, at ALT Linux we have rather strict packaging
requirements (no arch-specific data in /usr/share, etc) -- the package
will simply not build if you don't hold to them, so my build might be
different in some things from the community one.
Anyway I am still interested in discussing the packaging things in
right
way.
As a long time Debian user, I am a huge fan of packaging things
right. I am guessing that a lot of these policies will be very
similar, so it'd be good to share the effort. For example, I just
created a pd-extended.xml and pd-extended.desktop Free Desktop files
to handle the mime type, file association, menus, etc. Those are
certainly usable in most distros.
.hc
----------------------------------------------------------------------------
Access to computers should be unlimited and total. - the hacker ethic
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
