[opensuse-buildservice] A gnome package question for opensuse factory
What is the best (if there is one), to go along with the change in prefix for gnome applications. What is the exact change, it is from /opt/gnome to /usr, or is it different? What is the best way to deal with change? Is it possible to use the spec file for openSUSE-10.3 and for openSUSE prior to 10.3? Is it possible to update the gnome explanation on this wiki http://en.opensuse.org/SUSE_Build_Tutorial#Gnome_Packages page? It still uses the old /opt/gnome prefix. I need to update gramps to become aware of the prefix change: http://build.opensuse.org/package/show?package=gramps-beta&project=home%3Arbos -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Richard Bos píše v Ne 25. 03. 2007 v 21:17 +0200:
What is the best (if there is one), to go along with the change in prefix for gnome applications. What is the exact change, it is from /opt/gnome to /usr, or is it different?
Move from /opt/gnome to /usr. Move to new (and correct) gconf scriptlets instead of old scriptlets keeping orphans, And from technical aspect of view: Spec file cleanup. Use of %configure and RPM macros for default paths (except libexecdir).
What is the best way to deal with change? Is it possible to use the spec file for openSUSE-10.3 and for openSUSE prior to 10.3?
Yes, but such spec file looks unreadable containing much %if %suse_version: Preamble: %if %suse_version > 1020 %gconf_schemas_prereq %else PreReq: gconf2 %endif Configure: branch it dependently on prefix %install For > 1020 call %find_gconf_schemas. Scriptlets: For old versions use manually written %post, for newer the new three scriptlet macros. File list: For new version include autogenerated schemas files list, for older versions use explicit list.
Is it possible to update the gnome explanation on this wiki http://en.opensuse.org/SUSE_Build_Tutorial#Gnome_Packages page? It still uses the old /opt/gnome prefix.
Yes, it really needs update.
I need to update gramps to become aware of the prefix change: http://build.opensuse.org/package/show?package=gramps-beta&project=home%3Arbos
You can test it also in 10.2 + GNOME:UNSTABLE Build Service. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Op Monday 26 March 2007 12:38:07 schreef u:
What is the best way to deal with change? Is it possible to use the spec file for openSUSE-10.3 and for openSUSE prior to 10.3?
Yes, but such spec file looks unreadable containing much %if %suse_version:
How to deal with this than? Is it possible to have 2 spec files in the BS and use one depending on the opensuse version??? I don't think so, and there it is most likely required to use the %if %suse_version construction, isn't it???
Is it possible to update the gnome explanation on this wiki http://en.opensuse.org/SUSE_Build_Tutorial#Gnome_Packages page? It still uses the old /opt/gnome prefix.
Yes, it really needs update.
will you do that? -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Richard Bos píše v Po 26. 03. 2007 v 12:59 +0200:
Op Monday 26 March 2007 12:38:07 schreef u:
What is the best way to deal with change? Is it possible to use the spec file for openSUSE-10.3 and for openSUSE prior to 10.3?
Yes, but such spec file looks unreadable containing much %if %suse_version:
How to deal with this than? Is it possible to have 2 spec files in the BS and use one depending on the opensuse version??? I don't think so, and there it is most likely required to use the %if %suse_version construction, isn't it???
Yes, it is possible: 1. Create package foo with foo.spec and foo-old.spec. Enable it for FACTORY only. foo.spec will be used here by default. 2. Create package foo-old as a source link to package foo. foo-old.spec will be used here by default.
Is it possible to update the gnome explanation on this wiki http://en.opensuse.org/SUSE_Build_Tutorial#Gnome_Packages page? It still uses the old /opt/gnome prefix.
Yes, it really needs update.
will you do that?
It would be nice. There is many outdated parts, not only GNOME related. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 3/27/07, Stanislav Brabec
How to deal with this than? Is it possible to have 2 spec files in the BS and use one depending on the opensuse version??? I don't think so, and there it is most likely required to use the %if %suse_version construction, isn't it???
Yes, it is possible:
1. Create package foo with foo.spec and foo-old.spec. Enable it for FACTORY only. foo.spec will be used here by default.
2. Create package foo-old as a source link to package foo. foo-old.spec will be used here by default.
This is kind of a hack, though. It would be nice if this was more cleanly supported within a single package in the build service. Joe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Joe Shaw píše v Út 27. 03. 2007 v 12:26 -0400:
Hi,
On 3/27/07, Stanislav Brabec
wrote: How to deal with this than? Is it possible to have 2 spec files in the BS and use one depending on the opensuse version??? I don't think so, and there it is most likely required to use the %if %suse_version construction, isn't it???
Yes, it is possible:
1. Create package foo with foo.spec and foo-old.spec. Enable it for FACTORY only. foo.spec will be used here by default.
2. Create package foo-old as a source link to package foo. foo-old.spec will be used here by default.
This is kind of a hack, though. It would be nice if this was more cleanly supported within a single package in the build service.
I guess, that using link is a the standard way to implement more spec files in the Build Service. Well, here is a less hacky way: 1. Create package foo with foo.spec. Enable it for FACTORY only. foo.spec will be used here by default. 2. Link this package to foo-old. 3. Place new spec file into the foo-old. 4. Edit _link file and say, that you want to build from foo.spec, not foo-old.spec. 5. Enable foo-old only for older products. FYI: I rewrote my sync scripts. Now it uses just these package links for packages with more than one spec in the Autobuild repository. For example see GNOME:UNSTABLE freetype2 x ft2demos. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
hey guys, Anyone seen this? http://linuxmce.com/ I thought it was cool enough to download. just in case I decided to stoop down to loading a copy of Ubuntu on a spare PC with TV tuner card. any chance some one here would translate to SUSE? fxrsliberty --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hey,
On 3/28/07, Stanislav Brabec
I guess, that using link is a the standard way to implement more spec files in the Build Service.
It seems like it could be a lot simpler to the end user. It seems to be a question that comes up fairly often on the list, and while I think we'd all ideally see a single spec file for all platforms, it just isn't always practical. Moreover, it seems to be largely undocumented as the blessed way to do this.
Well, here is a less hacky way: 1. Create package foo with foo.spec. Enable it for FACTORY only. foo.spec will be used here by default. 2. Link this package to foo-old. 3. Place new spec file into the foo-old. 4. Edit _link file and say, that you want to build from foo.spec, not foo-old.spec. 5. Enable foo-old only for older products.
Yikes. This seems even more hacky. Editing _link files and such? I'd prefer a checkbox in the web UI and an osc command. :) Joe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Joe Shaw píše v St 28. 03. 2007 v 14:35 -0400:
Hey,
On 3/28/07, Stanislav Brabec
wrote: I guess, that using link is a the standard way to implement more spec files in the Build Service.
It seems like it could be a lot simpler to the end user. It seems to be a question that comes up fairly often on the list, and while I think we'd all ideally see a single spec file for all platforms, it just isn't always practical. Moreover, it seems to be largely undocumented as the blessed way to do this.
Well, here is a less hacky way: 1. Create package foo with foo.spec. Enable it for FACTORY only. foo.spec will be used here by default. 2. Link this package to foo-old. 3. Place new spec file into the foo-old. 4. Edit _link file and say, that you want to build from foo.spec, not foo-old.spec. 5. Enable foo-old only for older products.
Yikes. This seems even more hacky. Editing _link files and such? I'd prefer a checkbox in the web UI and an osc command. :)
The _link file is created by the "osc linkpac" and is created inside the repository instead of copy of sources. It allows much more than only building source from another spec file. You can define there additional patch, which will be applied to the sources or spec file, which may be interesting, if you want to package more similar versions or packages. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 3/28/07, Stanislav Brabec
The _link file is created by the "osc linkpac" and is created inside the repository instead of copy of sources. It allows much more than only building source from another spec file. You can define there additional patch, which will be applied to the sources or spec file, which may be interesting, if you want to package more similar versions or packages.
I can understand and appreciate the flexibility of using the _link files, but I don't feel like I'm getting my point across. The simple fact that you have to link package "foo" to "foo-fedora" or something along those lines is a hack. In the same sense that you have one spec file for SUSE and a .dsc file for Ubuntu within the same package, it would make a lot of sense to have one spec file for SUSE and one for Fedora *in the same package*. Or in the case of the GNOME move to /usr, one for pre-10.3 and one for 10.3 and later. I'm not a packaging guru, so I don't really want to spend my time creating a unified spec file. What I would like to do is pull the spec files from openSUSE and Fedora, update the version numbers and a tweak a few files inside it and go. There's no *easy* way to do this today, which I think somewhat limits the cross-platform usefulness of the build service. Thanks, Joe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
hi, did you know that you can have spec files per repository? for more see: http://build.opensuse.org/package/show?package=net-snmp-main-snapshot&project=net-snmp darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 3/28/07, Marcus Rueckert
did you know that you can have spec files per repository?
for more see: http://build.opensuse.org/package/show?package=net-snmp-main-snapshot&project=net-snmp
I didn't know this, no! Thanks for the link. Can we add this to the wiki somewhere? Is there any plan to support multiple repos for a single spec file? That would be even better. Joe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2007-03-28 17:08:45 -0400, Joe Shaw wrote:
On 3/28/07, Marcus Rueckert
wrote: did you know that you can have spec files per repository?
for more see: http://build.opensuse.org/package/show?package=net-snmp-main-snapshot&project=net-snmp
I didn't know this, no! Thanks for the link. Can we add this to the wiki somewhere?
there is a buildservice tips and tricks page. ;) and it is a wiki. you can edit it on your own!:)
Is there any plan to support multiple repos for a single spec file? That would be even better.
mls is on vacation atm. :D so we need to wait. =) darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 3/28/07, Marcus Rueckert
I didn't know this, no! Thanks for the link. Can we add this to the wiki somewhere?
there is a buildservice tips and tricks page. ;) and it is a wiki. you can edit it on your own!:)
Indeed. Often the problem is finding where on the wiki to add it. Thanks for the pointer, I've added it to the tips and tricks page. Joe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Op Tuesday 27 March 2007 13:38:40 schreef u:
How to deal with this than? Is it possible to have 2 spec files in the BS and use one depending on the opensuse version??? I don't think so, and there it is most likely required to use the %if %suse_version construction, isn't it???
Yes, it is possible:
1. Create package foo with foo.spec and foo-old.spec. Enable it for FACTORY only. foo.spec will be used here by default.
2. Create package foo-old as a source link to package foo. foo-old.spec will be used here by default.
But, the package foo in my case gramps does already exist and users have it (most likely) already configured in their pkg mngt application. As such I can't create the package gramps to hold FACTORY only. Now I could call it gramps-new, but than I have a problem in the (far) future when then package gramps has become obsolete and gramps-new is not new anymore. This does not seem to be right approach...., is there another way to deal with the new gnome prefix (or kde4 prefix)? Or should one just live with the %if %suse_version > 1020 and 1 spec file approach? -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (5)
-
James Tremblay
-
Joe Shaw
-
Marcus Rueckert
-
Richard Bos
-
Stanislav Brabec