noarch and %{_libdir} issues on 64-bit platforms
 

Hello All!

If someone tries to package executable script (arch-neytral) which must be placed into %{_libdir}/something (for example, nagios-plugin which must go into %{_libdir}/nagios/plugins ), he quickly founds that he actually can't mark package as noarch, because on both 32- and 64-bit systems %{_libdir} points to /usr/lib . There is an obvious workaround - not to mark the package as noarch.


How to overcome this issue and package utility as noarch?

See details:
* https://bugzilla.redhat.com/show_bug.cgi?id=423821#c5

* noarch build:

* http://koji.fedoraproject.org/koji/taskinfo?taskID=696176
* build w/o "BuildArch:***** noarch":
* http://koji.fedoraproject.org/koji/taskinfo?taskID=696178

--
With best regards!
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

noarch and %{_libdir} issues on 64-bit platforms
 

Quoth Peter Lemenkov:
> Hello All!
>
> If someone tries to package executable script (arch-neytral) which must be
> placed into %{_libdir}/something (for example, nagios-plugin which must go
> into %{_libdir}/nagios/plugins ), he quickly founds that he actually can't
> mark package as noarch, because on both 32- and 64-bit systems %{_libdir}
> points to /usr/lib . There is an obvious workaround - not to mark the
> package as noarch.
>
> How to overcome this issue and package utility as noarch?
>
> See details:
> * https://bugzilla.redhat.com/show_bug.cgi?id=423821#c5
>
> * noarch build:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=696176
> * build w/o "BuildArch: noarch":
> http://koji.fedoraproject.org/koji/taskinfo?taskID=696178

If it goes in /usr/lib and /usr/lib64 depending on arch, it's not noarch.

I think. People who are more confident about this ought to reply.

Regards,
--
Conrad Meyer <konrad@tylerc.org>
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

noarch and %{_libdir} issues on 64-bit platforms
 

Le Lun 7 juillet 2008 18:41, Peter Lemenkov a écrit :
> Hello All!
>
> If someone tries to package executable script (arch-neytral) which
> must be placed into %{_libdir}/something

If it's really arch-neutral its place is in /usr/share/sotmething not
libdir

--
Nicolas Mailhot

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

noarch and %{_libdir} issues on 64-bit platforms
 

On Monday 07 July 2008, Nicolas Mailhot wrote:
> Le Lun 7 juillet 2008 18:41, Peter Lemenkov a écrit :
> > Hello All!
> >
> > If someone tries to package executable script (arch-neytral) which
> > must be placed into %{_libdir}/something
>
> If it's really arch-neutral its place is in /usr/share/sotmething not
> libdir

Somewhere in %{_libexecdir} would work too.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

noarch and %{_libdir} issues on 64-bit platforms
 

On Monday 07 July 2008 18:41:31 Peter Lemenkov wrote:

> If someone tries to package executable script (arch-neytral) which must be
> placed into %{_libdir}/something (for example, nagios-plugin which must go

> How to overcome this issue and package utility as noarch?

I guess the problem here is that you want to put the executable
below %{_libdir}, afaik executables should go below %{_libexecdir}. But I
guess that nagios needs to be patched to use %{_libexecdir}, which is the
same for i386 and x86_64 afaik and should not hurt, because %{_bindir} is
also the same on both archs.

Regards,
Till
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list