[opensuse-buildservice] AdrianS , Could you please, set the ppc filter for MonoOSC in openSUSE:Factory:Contrib?
Hi -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
I forget to ask about RpmSpecManager and SyntaxHighlighting too :-)
which are MonoOSC dependency's
2009/9/30 Petit Eric
Hi
-- Cordially.
Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Petit Eric napsal(a):
I forget to ask about RpmSpecManager and SyntaxHighlighting too :-) which are MonoOSC dependency's
Is there a reason why the packages aren't noarch? Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2009/9/30 Michal Marek
Petit Eric napsal(a):
I forget to ask about RpmSpecManager and SyntaxHighlighting too :-) which are MonoOSC dependency's
Is there a reason why the packages aren't noarch? Not specialy, i just need to folow the Mono Framework, on some distro is in the /usr/lib64 rather /usr/lib
Michal
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious Sent from Bordeaux, France -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 30 of September 2009 12:39:15 Michal Marek wrote:
Petit Eric napsal(a):
I forget to ask about RpmSpecManager and SyntaxHighlighting too :-) which are MonoOSC dependency's
Is there a reason why the packages aren't noarch?
Michal
Yes, the reason is the AOT - Ahead Of Time - compile. Explanation from Mono Packaging Guidelines [1] """ The main reason for this is that mono can ahead-of-time compile its assemblies into ELF shared objects. These AOTs have to exist in the same directory as their DLL/EXE counterparts otherwise mono cannot use them. Even if we, as packagers, choose not to create the AOT files when we build the mono rpms, the system administrator can choose to create them after install. Since there's no way to place the mono assemblies into an arch independent directory and the AOTs into arch dependent directories, the whole thing has to go into an arch dependent tree. """ It's the similar as packages compiled with gcj's aot compiler are arch dependent, even if they're written in Java, just SUSE did not use it for Java. BTW: in times of rpm-4.7 it should be possible to improve mono to be able read noarch files from different location that AOT ones. [1] http://en.opensuse.org/Packaging/Mono Regards Michal Vyskocil
On Wednesday 30 of September 2009 11:20:29 Petit Eric wrote:
Hi
It would be better to use proper opensuse-contrib ML instead of this one. Adrian is not a maintainer of Contrib. Anyway I'm not sure what do you want to do with MonoOSC. Do yo want to remove ppc/ppc64 from package meta? Or something else? Why? ppc build does not work in OBS, so there's no reason o do that. Regards Michal Vyskocil
2009/9/30 Michal Vyskocil
On Wednesday 30 of September 2009 11:20:29 Petit Eric wrote:
Hi
It would be better to use proper opensuse-contrib ML instead of this one. Adrian is not a maintainer of Contrib.
Anyway I'm not sure what do you want to do with MonoOSC. Do yo want to remove ppc/ppc64 from package meta? Or something else? Why? ppc build does not work in OBS, so there's no reason o do that. seems to be a filter problem, i prefer keep it for Mac
Regards Michal Vyskocil
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Michal Vyskocil napsal(a):
On Wednesday 30 of September 2009 12:39:15 Michal Marek wrote:
Petit Eric napsal(a):
I forget to ask about RpmSpecManager and SyntaxHighlighting too :-) which are MonoOSC dependency's Is there a reason why the packages aren't noarch?
Michal
Yes, the reason is the AOT - Ahead Of Time - compile. Explanation from Mono Packaging Guidelines [1]
""" The main reason for this is that mono can ahead-of-time compile its assemblies into ELF shared objects. These AOTs have to exist in the same directory as their DLL/EXE counterparts otherwise mono cannot use them. Even if we, as packagers, choose not to create the AOT files when we build the mono rpms, the system administrator can choose to create them after install. Since there's no way to place the mono assemblies into an arch independent directory and the AOTs into arch dependent directories, the whole thing has to go into an arch dependent tree. """
We have noarch mono packages in Factory. Are these broken then? Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 30 of September 2009 13:23:27 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 11:20:29 Petit Eric wrote:
Hi
It would be better to use proper opensuse-contrib ML instead of this one. Adrian is not a maintainer of Contrib.
Anyway I'm not sure what do you want to do with MonoOSC. Do yo want to remove ppc/ppc64 from package meta? Or something else? Why? ppc build does not work in OBS, so there's no reason o do that.
seems to be a filter problem, i prefer keep it for Mac
Sorry, but I still don't know what you'd like to do. Please be more verbose. What do you mean by term 'filter'? Do you want to enable - or disable ppc build of MonoOSC? Or I'm completely wrong? BTW: As I know the ppc builds are not able in OBS. Regards Michal Vyskocil
On Wednesday 30 of September 2009 13:23:27 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 11:20:29 Petit Eric wrote:
Hi
It would be better to use proper opensuse-contrib ML instead of this one. Adrian is not a maintainer of Contrib.
Anyway I'm not sure what do you want to do with MonoOSC. Do yo want to remove ppc/ppc64 from package meta? Or something else? Why? ppc build does not work in OBS, so there's no reason o do that.
seems to be a filter problem, i prefer keep it for Mac
Sorry, but I still don't know what you'd like to do. Please be more verbose. What do you mean by term 'filter'? Do you want to enable - or disable ppc build of MonoOSC? Or I'm completely wrong? I would like to enable ppc for MonoOSC, RpmSpecManager and SyntaxHighlighting, the term filter came from IRC chat : (11:16:27) dl9pf:
2009/9/30 Michal Vyskocil
BTW: As I know the ppc builds are not able in OBS.
Regards Michal Vyskocil
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 30 of September 2009 14:05:41 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 13:23:27 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 11:20:29 Petit Eric wrote:
Hi
It would be better to use proper opensuse-contrib ML instead of this one. Adrian is not a maintainer of Contrib.
Anyway I'm not sure what do you want to do with MonoOSC. Do yo want to remove ppc/ppc64 from package meta? Or something else? Why? ppc build does not work in OBS, so there's no reason o do that.
seems to be a filter problem, i prefer keep it for Mac
Sorry, but I still don't know what you'd like to do. Please be more verbose. What do you mean by term 'filter'? Do you want to enable - or disable ppc build of MonoOSC? Or I'm completely wrong?
I would like to enable ppc for MonoOSC, RpmSpecManager and SyntaxHighlighting, the term filter came from IRC chat : (11:16:27) dl9pf: the ppc filter needs to be set by adrianS iirc
Well, now I understand, then maybe bounce the email to directly adrian :) MV
BTW: As I know the ppc builds are not able in OBS.
Regards Michal Vyskocil
2009/9/30 Michal Vyskocil
On Wednesday 30 of September 2009 14:05:41 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 13:23:27 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 11:20:29 Petit Eric wrote:
Hi
It would be better to use proper opensuse-contrib ML instead of this one. Adrian is not a maintainer of Contrib.
Anyway I'm not sure what do you want to do with MonoOSC. Do yo want to remove ppc/ppc64 from package meta? Or something else? Why? ppc build does not work in OBS, so there's no reason o do that.
seems to be a filter problem, i prefer keep it for Mac
Sorry, but I still don't know what you'd like to do. Please be more verbose. What do you mean by term 'filter'? Do you want to enable - or disable ppc build of MonoOSC? Or I'm completely wrong?
I would like to enable ppc for MonoOSC, RpmSpecManager and SyntaxHighlighting, the term filter came from IRC chat : (11:16:27) dl9pf: the ppc filter needs to be set by adrianS iirc
Well, now I understand, then maybe bounce the email to directly adrian :) I don't have his email
MV
BTW: As I know the ppc builds are not able in OBS.
Regards Michal Vyskocil
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Michal Marek napsal(a):
Michal Vyskocil napsal(a):
On Wednesday 30 of September 2009 12:39:15 Michal Marek wrote:
Petit Eric napsal(a):
I forget to ask about RpmSpecManager and SyntaxHighlighting too :-) which are MonoOSC dependency's Is there a reason why the packages aren't noarch?
Michal
Yes, the reason is the AOT - Ahead Of Time - compile. Explanation from Mono Packaging Guidelines [1]
""" The main reason for this is that mono can ahead-of-time compile its assemblies into ELF shared objects. These AOTs have to exist in the same directory as their DLL/EXE counterparts otherwise mono cannot use them. Even if we, as packagers, choose not to create the AOT files when we build the mono rpms, the system administrator can choose to create them after install. Since there's no way to place the mono assemblies into an arch independent directory and the AOTs into arch dependent directories, the whole thing has to go into an arch dependent tree. """
We have noarch mono packages in Factory. Are these broken then?
BTW, if we install mono assemblies into /usr/lib on all platforms and mark the packages noarch, I don't see how that breaks the above use-case. /usr/lib cannot be nfs-shared anyway, so there is no problem if an admin puts aot-compiled native files there. IMO the policy should be changed, there is no win in duplicating the files in /usr/lib and /usr/lib64. Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 30 of September 2009 13:32:34 Michal Marek wrote:
Michal Vyskocil napsal(a):
On Wednesday 30 of September 2009 12:39:15 Michal Marek wrote:
Petit Eric napsal(a):
I forget to ask about RpmSpecManager and SyntaxHighlighting too :-) which are MonoOSC dependency's
Is there a reason why the packages aren't noarch?
Michal
Yes, the reason is the AOT - Ahead Of Time - compile. Explanation from Mono Packaging Guidelines [1]
""" The main reason for this is that mono can ahead-of-time compile its assemblies into ELF shared objects. These AOTs have to exist in the same directory as their DLL/EXE counterparts otherwise mono cannot use them. Even if we, as packagers, choose not to create the AOT files when we build the mono rpms, the system administrator can choose to create them after install. Since there's no way to place the mono assemblies into an arch independent directory and the AOTs into arch dependent directories, the whole thing has to go into an arch dependent tree. """
We have noarch mono packages in Factory. Are these broken then?
Technically not unless they don't use AOT compilation - afaik it is not necessary (but I don't know a much about mono things). But on the other side they don't conform the current policy (even if the guidelines are not completed and are just semi-official, we don't have anything better for Mono packages). Michal Vyskocil
2009/9/30 Michal Marek
Michal Marek napsal(a):
Michal Vyskocil napsal(a):
On Wednesday 30 of September 2009 12:39:15 Michal Marek wrote:
Petit Eric napsal(a):
I forget to ask about RpmSpecManager and SyntaxHighlighting too :-) which are MonoOSC dependency's Is there a reason why the packages aren't noarch?
Michal
Yes, the reason is the AOT - Ahead Of Time - compile. Explanation from Mono Packaging Guidelines [1]
""" The main reason for this is that mono can ahead-of-time compile its assemblies into ELF shared objects. These AOTs have to exist in the same directory as their DLL/EXE counterparts otherwise mono cannot use them. Even if we, as packagers, choose not to create the AOT files when we build the mono rpms, the system administrator can choose to create them after install. Since there's no way to place the mono assemblies into an arch independent directory and the AOTs into arch dependent directories, the whole thing has to go into an arch dependent tree. """
We have noarch mono packages in Factory. Are these broken then?
BTW, if we install mono assemblies into /usr/lib on all platforms and mark the packages noarch, I don't see how that breaks the above use-case. /usr/lib cannot be nfs-shared anyway, so there is no problem if an admin puts aot-compiled native files there. IMO the policy should be changed, there is no win in duplicating the files in /usr/lib and /usr/lib64. yes duplicate isn't a good solution, but Mono like MS .Net work around GAC, see gacutil :-)
Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious Sent from Paris, France -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 30 September 2009 16:35:16 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 14:05:41 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 13:23:27 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 11:20:29 Petit Eric wrote: > Hi
It would be better to use proper opensuse-contrib ML instead of this one. Adrian is not a maintainer of Contrib.
Anyway I'm not sure what do you want to do with MonoOSC. Do yo want to remove ppc/ppc64 from package meta? Or something else? Why? ppc build does not work in OBS, so there's no reason o do that.
seems to be a filter problem, i prefer keep it for Mac
Sorry, but I still don't know what you'd like to do. Please be more verbose. What do you mean by term 'filter'? Do you want to enable - or disable ppc build of MonoOSC? Or I'm completely wrong?
I would like to enable ppc for MonoOSC, RpmSpecManager and SyntaxHighlighting, the term filter came from IRC chat : (11:16:27) dl9pf: the ppc filter needs to be set by adrianS iirc
Well, now I understand, then maybe bounce the email to directly adrian :)
I don't have his email
He's on vacation this week, and I expect that he reads this and reacts early next week. If not, please open a bug (follow http://bugs.opensuse.org) against the openSUSE project, component Build Service and ask for the change. Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
2009/9/30 Andreas Jaeger
On Wednesday 30 September 2009 16:35:16 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 14:05:41 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 13:23:27 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: > On Wednesday 30 of September 2009 11:20:29 Petit Eric wrote: >> Hi > > It would be better to use proper opensuse-contrib ML instead of > this one. Adrian is not a maintainer of Contrib. > > Anyway I'm not sure what do you want to do with MonoOSC. Do yo want > to remove ppc/ppc64 from package meta? Or something else? Why? ppc > build does not work in OBS, so there's no reason o do that. seems to be a filter problem, i prefer keep it for Mac
Sorry, but I still don't know what you'd like to do. Please be more verbose. What do you mean by term 'filter'? Do you want to enable - or disable ppc build of MonoOSC? Or I'm completely wrong?
I would like to enable ppc for MonoOSC, RpmSpecManager and SyntaxHighlighting, the term filter came from IRC chat : (11:16:27) dl9pf: the ppc filter needs to be set by adrianS iirc
Well, now I understand, then maybe bounce the email to directly adrian :)
I don't have his email
He's on vacation this week, and I expect that he reads this and reacts early next week.
If not, please open a bug (follow http://bugs.opensuse.org) against the openSUSE project, component Build Service and ask for the change. No problems, i have all the time :-)
Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Sep 30, 2009 at 05:24:52PM +0200, Andreas Jaeger wrote:
On Wednesday 30 September 2009 16:35:16 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 14:05:41 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: On Wednesday 30 of September 2009 13:23:27 Petit Eric wrote:
2009/9/30 Michal Vyskocil
: > On Wednesday 30 of September 2009 11:20:29 Petit Eric wrote: >> Hi > > It would be better to use proper opensuse-contrib ML instead of > this one. Adrian is not a maintainer of Contrib. > > Anyway I'm not sure what do you want to do with MonoOSC. Do yo want > to remove ppc/ppc64 from package meta? Or something else? Why? ppc > build does not work in OBS, so there's no reason o do that. seems to be a filter problem, i prefer keep it for Mac
Sorry, but I still don't know what you'd like to do. Please be more verbose. What do you mean by term 'filter'? Do you want to enable - or disable ppc build of MonoOSC? Or I'm completely wrong?
I would like to enable ppc for MonoOSC, RpmSpecManager and SyntaxHighlighting, the term filter came from IRC chat : (11:16:27) dl9pf: the ppc filter needs to be set by adrianS iirc
Well, now I understand, then maybe bounce the email to directly adrian :)
I don't have his email
He's on vacation this week, and I expect that he reads this and reacts early next week.
If not, please open a bug (follow http://bugs.opensuse.org) against the openSUSE project, component Build Service and ask for the change.
Since PowerPC does not build in chroots (aka "fully unprotected"), we only enable PowerPC builds for openSUSE:Factory only. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (5)
-
Andreas Jaeger
-
Marcus Meissner
-
Michal Marek
-
Michal Vyskocil
-
Petit Eric