[opensuse-packaging] Is it ok to use /opt?
Hi, I'm putting together a libraw1394-8 package to satisfy old packages (which should be fixed) is it ok to use --prefix=/opt for it? I've redefined a couple of macros for this. home:plater libraw1394-8 Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 19/11/10 11:39, Dave Plater wrote:
Hi, I'm putting together a libraw1394-8 package to satisfy old packages (which should be fixed) is it ok to use --prefix=/opt for it? I've redefined a couple of macros for this. home:plater libraw1394-8 Thanks Dave P
No, /opt is reserved for 3rd party vendors packages (e.g Google Picasa) that are usually distributed in binary form and cannot be built from source. -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
El 19/11/10 07:39, Dave Plater escribió:
Hi, I'm putting together a libraw1394-8 package to satisfy old packages (which should be fixed) is it ok to use --prefix=/opt for it? I've redefined a couple of macros for this. home:plater libraw1394-8 Thanks Dave P
No, use the library packaging policy for such matters. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, I'd like to chime in, with my own question. On 11/19/2010 08:00 AM, Cristian Rodríguez wrote:
El 19/11/10 07:39, Dave Plater escribió:
Hi, I'm putting together a libraw1394-8 package to satisfy old packages (which should be fixed) is it ok to use --prefix=/opt for it? I've redefined a couple of macros for this. home:plater libraw1394-8 Thanks Dave P
No, use the library packaging policy for such matters.
What if that doesn't work? I am struggling with axis2c which is needed by Eucalyptus. Axis2c has the very annoying problem that it cannot be installed in an FHS compliant way. Fixing the axis2c code to address this issue is way out of scope. Axis2c does allow a split setup, where core libraries are in %{_libdir} and transport layer libraries are in "specialdir", where "specialdir" = $AXIS2C_HOME/lib. Now $AXIS2C_HOME can be anywhere, /opt appears to be the logical choice but I am more than happy to put it somewhere else. So, where should it live? Considering there is no getting around having "specialdir" is it even worth the effort of splitting the axis2c libraries into core libs to be installed in %{_libdir} and transport layer libs to be installed in "specialdir" Help is appreciated. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Software Engineer Consultant LINUX rschweikert@novell.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
* Robert Schweikert (rschweikert@novell.com) [20101119 14:56]:
Fixing the axis2c code to address this issue is way out of scope.
Why would that be out of scope? At least in the past, this has been part of a maintainers job? Have you checked axis2c in other distributions to see how they solve the problem? Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Robert Schweikert wrote:
On 11/19/2010 08:00 AM, Cristian Rodríguez wrote:
El 19/11/10 07:39, Dave Plater escribió:
Hi, I'm putting together a libraw1394-8 package to satisfy old packages (which should be fixed) is it ok to use --prefix=/opt for it? I've redefined a couple of macros for this. home:plater libraw1394-8 Thanks Dave P
No, use the library packaging policy for such matters.
What if that doesn't work? I am struggling with axis2c which is needed by Eucalyptus. Axis2c has the very annoying problem that it cannot be installed in an FHS compliant way. Fixing the axis2c code to address this issue is way out of scope. Axis2c does allow a split setup, where core libraries are in %{_libdir} and transport layer libraries are in "specialdir", where "specialdir" = $AXIS2C_HOME/lib.
It's legal to use /usr/lib/$something and have an application specific fs layout below that. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 11/22/2010 10:00 AM, Ludwig Nussel wrote:
Robert Schweikert wrote:
On 11/19/2010 08:00 AM, Cristian Rodríguez wrote:
El 19/11/10 07:39, Dave Plater escribió:
Hi, I'm putting together a libraw1394-8 package to satisfy old packages (which should be fixed) is it ok to use --prefix=/opt for it? I've redefined a couple of macros for this. home:plater libraw1394-8 Thanks Dave P
No, use the library packaging policy for such matters.
What if that doesn't work? I am struggling with axis2c which is needed by Eucalyptus. Axis2c has the very annoying problem that it cannot be installed in an FHS compliant way. Fixing the axis2c code to address this issue is way out of scope. Axis2c does allow a split setup, where core libraries are in %{_libdir} and transport layer libraries are in "specialdir", where "specialdir" = $AXIS2C_HOME/lib.
It's legal to use /usr/lib/$something and have an application specific fs layout below that.
cu Ludwig
Fortunately there's no need for libraw1394-8 anymore, pwlib has been altered to use only v4linux for video. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 11/22/2010 03:00 AM, Ludwig Nussel wrote:
Robert Schweikert wrote:
On 11/19/2010 08:00 AM, Cristian Rodríguez wrote:
El 19/11/10 07:39, Dave Plater escribió:
Hi, I'm putting together a libraw1394-8 package to satisfy old packages (which should be fixed) is it ok to use --prefix=/opt for it? I've redefined a couple of macros for this. home:plater libraw1394-8 Thanks Dave P
No, use the library packaging policy for such matters.
What if that doesn't work? I am struggling with axis2c which is needed by Eucalyptus. Axis2c has the very annoying problem that it cannot be installed in an FHS compliant way. Fixing the axis2c code to address this issue is way out of scope. Axis2c does allow a split setup, where core libraries are in %{_libdir} and transport layer libraries are in "specialdir", where "specialdir" = $AXIS2C_HOME/lib.
It's legal to use /usr/lib/$something and have an application specific fs layout below that.
Thank you, that is just what I needed to hear/know.
cu Ludwig
-- Robert Schweikert MAY THE SOURCE BE WITH YOU Software Engineer Consultant LINUX rschweikert@novell.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (6)
-
Cristian Rodríguez -
Dave Plater -
Ludwig Nussel -
Pavol Rusnak -
pth＠suse.de -
Robert Schweikert