[opensuse-packaging] Mono packages...
Hi all, Gabriel recently asked me if I could maintain the Banshee Project repositories, which I accepted. Now this brings me a few issues... Banshee repository inherits some packages from Mono which seem to be based on what I would call 'fedora' specs and could use some love. Well, I'm available to improve a bit this packages (the ones used for Banshee) and resubmit them to Mono project, and then branch them over to Banshee. The reason why they are all there is because currently (and in the future) Banshee will be served to all supported platforms through those reps, so those mono packages provide the requirements for it. Now, there's two things I've noticed: 1. Mono packages are 'noarch' and install always on /usr/lib (which suggests %libexecdir can be used); 2. Mono packages are placing the .pc file on /usr/share/pkgconfig; 3. Mono packages have sometimes a devel package which only provides the .pc file and no real development files. My questions are quite simple: 1. Can we use a '%define _libdir %{libexecdir}? This would make the packages always install on /usr/lib (or as an alternative, '%define _libdir %{prefix}/lib'); 2. Why would we want to drop the .pc file on /usr/share? If we would use the macro above, shouldn't it also be sane to dump the .pc file on /usr/lib/pkgconfig ? 3. In the cases where we have a devel package only for the .pc file, could we merge it and have a 'Provides: %{name}-devel' ? I really would love to make the best possible for Banshee repositories, and sorting out this mono things would be something really cool. Any help/comments will be appreciated. NM -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le samedi 28 mai 2011, à 02:11 +0100, Nelson Marques a écrit :
My questions are quite simple:
1. Can we use a '%define _libdir %{libexecdir}? This would make the packages always install on /usr/lib (or as an alternative, '%define _libdir %{prefix}/lib');
I don't understand. Why not use %{_libexecdir} directly?
2. Why would we want to drop the .pc file on /usr/share? If we would use the macro above, shouldn't it also be sane to dump the .pc file on /usr/lib/pkgconfig ?
That's how pkg-config works: arch-independent .pc files go to /usr/share/pkgconfig. So it's right the current way.
3. In the cases where we have a devel package only for the .pc file, could we merge it and have a 'Provides: %{name}-devel' ?
We could, yes. Not sure if it's better or not; possibly a matter of taste. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Sat, May 28, 2011 at 03:35, Vincent Untz <vuntz@opensuse.org> wrote:
Le samedi 28 mai 2011, à 02:11 +0100, Nelson Marques a écrit :
My questions are quite simple:
1. Can we use a '%define _libdir %{libexecdir}? This would make the packages always install on /usr/lib (or as an alternative, '%define _libdir %{prefix}/lib');
I don't understand. Why not use %{_libexecdir} directly?
2. Why would we want to drop the .pc file on /usr/share? If we would use the macro above, shouldn't it also be sane to dump the .pc file on /usr/lib/pkgconfig ?
That's how pkg-config works: arch-independent .pc files go to /usr/share/pkgconfig. So it's right the current way.
3. In the cases where we have a devel package only for the .pc file, could we merge it and have a 'Provides: %{name}-devel' ?
We could, yes. Not sure if it's better or not; possibly a matter of taste.
Vincent
I don't remember the details, but the mono packages aren't that way by accident. I believe it has to do with the packages being noarch or something. - Stephen -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 28/05/11 11:35, Vincent Untz wrote:
Le samedi 28 mai 2011, à 02:11 +0100, Nelson Marques a écrit :
My questions are quite simple:
1. Can we use a '%define _libdir %{libexecdir}? This would make the packages always install on /usr/lib (or as an alternative, '%define _libdir %{prefix}/lib');
I don't understand. Why not use %{_libexecdir} directly?
I wanted to ask this question too. :-)
2. Why would we want to drop the .pc file on /usr/share? If we would use the macro above, shouldn't it also be sane to dump the .pc file on /usr/lib/pkgconfig ?
That's how pkg-config works: arch-independent .pc files go to /usr/share/pkgconfig. So it's right the current way.
+1
3. In the cases where we have a devel package only for the .pc file, could we merge it and have a 'Provides: %{name}-devel' ?
We could, yes. Not sure if it's better or not; possibly a matter of taste.
We should not, because installing SomeMonoApplication would install all it's development requirements which is not what you want. (It's probably OK if all mono devel packages contained only one .pc file, but I suppose that is not the case ...). -- 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
So this package[1] would be correctly packaged ? [1] - https://build.opensuse.org/package/view_file?file=dbus-sharp.spec&package=db... On Sun, May 29, 2011 at 2:11 PM, Pavol Rusnak <prusnak@opensuse.org> wrote:
On 28/05/11 11:35, Vincent Untz wrote:
Le samedi 28 mai 2011, à 02:11 +0100, Nelson Marques a écrit :
My questions are quite simple:
1. Can we use a '%define _libdir %{libexecdir}? This would make the packages always install on /usr/lib (or as an alternative, '%define _libdir %{prefix}/lib');
I don't understand. Why not use %{_libexecdir} directly?
I wanted to ask this question too. :-)
2. Why would we want to drop the .pc file on /usr/share? If we would use the macro above, shouldn't it also be sane to dump the .pc file on /usr/lib/pkgconfig ?
That's how pkg-config works: arch-independent .pc files go to /usr/share/pkgconfig. So it's right the current way.
+1
3. In the cases where we have a devel package only for the .pc file, could we merge it and have a 'Provides: %{name}-devel' ?
We could, yes. Not sure if it's better or not; possibly a matter of taste.
We should not, because installing SomeMonoApplication would install all it's development requirements which is not what you want. (It's probably OK if all mono devel packages contained only one .pc file, but I suppose that is not the case ...).
-- 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
-- Nelson Marques /* As cicatrizes lembram-nos de onde estivemos, mas não ditam para onde vamos */ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (4)
-
Nelson Marques -
Pavol Rusnak -
Stephen Shaw -
Vincent Untz