[opensuse-packaging] gecko-sdk
Hi everybody, For one of my packages I used to have a BuildRequires: gecko-sdk in my spec file. This worked great until recently. Is there a new Provides: for it available? It was pretty handy for not needing to 'clutter' the spec with hundreds of %ifs... Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, Dominique Leuenberger schrieb:
For one of my packages I used to have a BuildRequires: gecko-sdk in my spec file. This worked great until recently.
Is there a new Provides: for it available? It was pretty handy for not needing to 'clutter' the spec with hundreds of %ifs...
gecko-sdk was a package name in the first place for the "first" xulrunner package (based on Mozilla 1.8.0). Since then we have XULRunner 1.8.1.x and 1.9.0.x (in future 1.9.1.x) which have prefixed package names to be able to install them in parallel (a bit like shared lib package versioning). And as for example 1.8.1 to 1.9.0 is quite different when it comes to embedding it made no sense to have one name (gecko-sdk) since every package should explicitely tell against which version to build. Therefore you have to choose between mozilla-xulrunner181-devel or mozilla-xulrunner190-devel currently with mozilla-xulrunner191-devel coming up in mozilla:beta. Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi Wolfgang
On 1/7/2009 at 12:34 PM, Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote: Therefore you have to choose between mozilla-xulrunner181-devel or mozilla-xulrunner190-devel currently with mozilla-xulrunner191-devel coming up in mozilla:beta.
Thank you veyr much... it's awlays the same problems when using those XUL runners. I feel they are not as handy as they should be. Also for any random app to actually find the Libs, as they are moving around from one place to another (version specific information) and (for good reasons) are not in LD_LIBRARY_PATH.... Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi Wolfgang On Mittwoch 07 Januar 2009 12:34:32 Wolfgang Rosenauer wrote:
gecko-sdk was a package name in the first place for the "first" xulrunner package (based on Mozilla 1.8.0). Since then we have XULRunner 1.8.1.x and 1.9.0.x (in future 1.9.1.x) which have prefixed package names to be able to install them in parallel (a bit like shared lib package versioning). And as for example 1.8.1 to 1.9.0 is quite different when it comes to embedding it made no sense to have one name (gecko-sdk) since every package should explicitely tell against which version to build.
Therefore you have to choose between mozilla-xulrunner181-devel or mozilla-xulrunner190-devel currently with mozilla-xulrunner191-devel coming up in mozilla:beta.
What about people just want building their apps against the "default" mozilla-xulrunner package of a openSUSE distribution? I'm thinking about a construct like the one below in the corresponding project config like this: %if 0%{?suse_version} < 1100 Substitute: gecko-sdk mozilla-xulrunner181-devel %else Substitute: gecko-sdk mozilla-xulrunner190-devel %endif This way, people not needing a special xulrunner version can just use BuildRequires: gecko-sdk in their specfiles and add something like to above lines via: osc meta prjconf <project> -e to their OBS projects. Any objections from your side? With kind regards, Lars -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, Lars Vogdt schrieb:
What about people just want building their apps against the "default" mozilla-xulrunner package of a openSUSE distribution?
Tell me which is the "default" xulrunner on a specific openSUSE distribution ;-) IIRC we only have two in 11.0 and 11.1 and I can easily say that xulrunner190 is the "default" on 11.1 because 181 should have been dropped already. For 11.0 I can't easily say what the default should be. In theory the newest one should be the default since it's the longest supported one, but the biggest point still is: It's really hard to say what an application needs from xulrunner to build. For example 1.8.1.x and 1.9.0.x are really different if gtkmozembed is used (not speaking about the complete XRE) and an application most likely doesn't support both. People still can use the project config and define it just to help packaging and if it breaks they need to use the correct package explicitely. Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (3)
-
Dominique Leuenberger -
Lars Vogdt -
Wolfgang Rosenauer