- openSUSE Packaging

[opensuse-packaging] missing gtk2 engine
by Ed Hurst 05 Sep '06

05 Sep '06

Re: SuSE 10.1 x86-64 I notice the 32-bit package of gtk2 engines includes cleanice. The 64-bit package is missing it, though the documentation is there. Does anyone know if this was an oversight? Or is it because something in the engine source won't compile 64-bit? -- Ed Hurst ------------ Applied Bible - http://ed.asisaid.com/bible/index.html Plain & Simple Computer Help - http://ed.asisaid.com/ Mission, Method & Means blog - http://ed.asisaid.com/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

Re: [packagers] [opensuse-packaging] triggerd: idea how to get rid many SuSEconfig scripts and simplify scriptlets
by Klaus Kaempf 05 Sep '06

05 Sep '06

* Joe Shaw <joeshaw(a)novell.com> [Sep 05. 2006 18:08]: > Hi, > > On Mon, 2006-09-04 at 13:04 +0200, Stanislav Brabec wrote: > > Create a new daemon, running by default: triggerd > > Adding a daemon I think is a really bad idea. We have an overabundance > of daemons as it is. I think that a packaging daemon (rcd, zmd) is a > generally bad idea, and that's a lot more full-featured than something > which just runs scripts. (And I was one of its designers. Whoops.) A management daemon, supporting role based access (separation of duty), is highly desirable for enterprises. Looking at package management, solving dependencies is a resource intensive task. One can gain speed by constructing a proper in-memory representation of the dependency graph. However, this might take longer than the actual run of the dependency solver. A deamon, which keeps the graph representation in memory, is one possible approach to make package management fast. Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] triggerd: idea how to get rid many SuSEconfig scripts and simplify scriptlets
by Stanislav Brabec 04 Sep '06

04 Sep '06

Hallo. I have been thinking about getting rid many of SuSEconfig scripts and making scriptlets more effective (call them once per transaction instead of four times per package). Because modification of RPM seems to be not acceptable, I tried to find a solution, which will work with unmodified RPM: Create a new daemon, running by default: triggerd triggerd can be an inotify based software and will have a configuration in /etc/trigger.d/. Each file there will contain a list of paths. If anything in specified path will change, script with the same name will be started with arguments saying, which directory (and maybe which file) have been changed. Specified path can be file, directory or recursive directory search. There will be a special flag (file), which will block/postpone the script calling. Paths: /etc/trigger.d/*: Configuration files. /usr/lib/trigger/*: Trigger scripts. /var/lib/triggerd/postpone/*: Postpone flags. Postpone calling of scripts until file here disappears. This daemon can obsolete many SuSEconfig scripts and even make scriptlets run faster - for example ldconfig: /etc/trigger.d/ldconfig: Symlink to /etc/ld.co.conf /usr/lib/trigger/ldconfig: Probably symlink to /sbin/ldconfig %pre touch var/lib/triggerd/postpone/ldconfig %preun touch var/lib/triggerd/postpone/ldconfig %posttrans if !.....zypp_is_running... ; then rm var/lib/triggerd/postpone/ldconfig fi In zypp: After completing of "transaction": rm var/lib/triggerd/postpone/ldconfig Transaction stuff in zypp / yast is not yet connected with RPM, so this is a work-around. RPM %posttrans will detect, that YaST/zypp is running, and will not delete postpone flag. zypp will delete it, when it will reach end of the "transaction" (i. e. if PreReq of next package has to be resolved or package list is complete). This implementation can replace all ocurrences of ldconfig except calls in "self prerequiring" scriptlets - scriptlets, which require working binaries from the same package. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)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-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 4

[opensuse-packaging] Packaging libtool archives (*.la files)
by Andreas Hanke 31 Aug '06

31 Aug '06

Hi, while looking at various spec files, I noticed that it seems to become increasingly popular these days that libtool archives (*.la files) are removed from packages, by deleting them during the build or by using the %exclude directive or similar. Is there a general policy about this? The idea seems to come from Fedora, where this _is_ a general policy. I'd like to know whether we have a similar policy or whether each packager decides that himself. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] upstart for opensuse
by Marcus Rueckert 31 Aug '06

31 Aug '06

hi, http://www.netsplit.com/blog/work/canonical/upstart.html i did a plain package for it. sysv-rc is still missing. will do it once i am at home. :) package can be found in home:darix darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 1

[opensuse-packaging] xulrunner / gecko update
by Wolfgang Rosenauer 23 Aug '06

23 Aug '06

Hi, on SUSE Linux 10.1 we have the two packages mozilla-xulrunner and its devel package gecko-sdk to get the mozilla development environment for embedding gecko into other applications. (Gecko 1.8.0.x based) This has changed some time ago in FACTORY and now we have the following package structure: mozilla-xulrunner180 mozilla-xulrunner180-devel mozilla-xulrunner181 mozilla-xulrunner181-devel mozilla-xulrunner180 replaces the old mozilla-xulrunner and gecko-sdk packages by providing the correct RPM provides. So you didn't notice so far probably. If your package requires mozilla-xulrunner or needs gecko-sdk to build you should now change to one of the new names in Requires and BuildRequires. And in addition you should try to build against the 181 version which is a snapshot of the upcoming Gecko 1.8.1. If it's possible (means every application works with 1.8.1 we will drop the 1.8.0 version before 10.2) Wolfgang -- SUSE LINUX GmbH -o) Tel: +49-(0)911-740 53 0 Maxfeldstr. 5 /\\ Fax: +49-(0)911-740 53 679 90409 Nuernberg, Germany _\_v --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] packaging made simple.
by jdd 21 Aug '06

21 Aug '06

I began asking on factory for a simple way of packaging and the thread become long and interesting and probably better here. In fact the question comes actually to the spec file content. The example choosen is for a sh script. I will report on the wiki once done. summary: I asked for the simpler instructions to make an openSUSE rpm. I took as example the makethumb.sh script, because I like it and it's not already on openSUSE, and because a script is probably the simpler example one can find. don't forget this is just an example. If I should become officially packager for openSUSE and this script, I of course should first ask the author, but I won't bother him now. I would like to work as a packager as simple user on my computer (not root) if possible. so I build in ~/Document a "package" folder I add a makethumb.sh folder there, then in it sources rpm srpm directories in sources, I copy the three files I have from this package on my computer: makethumb.sh the main script comment.sh a personal utility related to it .makethumbrc the setup file I use I have doc, but did not include it at the time. Somebody send me an example spec file, I will comment it on an other post thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 17

[opensuse-packaging] Macro documentation
by Mauricio Teixeira (netmask) 14 Aug '06

14 Aug '06

Two situations, then the question. Situation #1. I was having trouble compiling a package today. I needed a patch to be applied if (and only if) the package would build on a 64 bit machine. I couldn't find any direct reference on how to do that on the spec. Someone on the IRC told me to use "%ifarch x86_64". Situation #2. Sometime back I was trying to build other package that would need different actions depending on the SUSE release. Again, someone on the IRC told me to use "%if %{?suse_version:1}0 >= 101". The question. Those are two simple examples of macros, and tips that would be very nice to have documented on the wiki. I've found that there is a "cross distribution how to", but it's very deep hidden on the wiki (there's no visible link to it, I found using the "category" pages"). So why not make a better documentation about it? I would love to help, but at this moment I don't have enough time, neither enough tech knowledge to help. :( -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net

6 8

[opensuse-packaging] KMP packages and updated kernels
by Bernhard Walle 13 Aug '06

13 Aug '06

Hello, I've backaged alsa-bluetooth.sf.net which requires a kernel module. It's in my repository home:bwalle. The problem is that this is built against the original kernel of SUSE 10.1 and not against the update kernel. This makes the mechanism a bit useless, because the user should always have installed the latest update kernel which is available by YOU, currently 2.6.16.21. Will this be fixed or am I doing something wrong? Thanks. Regards, Bernhard -- Was wir wissen, ist ein Tropfen; was wir nicht wissen, ein Ozean. -- Isaac Newton

2 1

[opensuse-packaging] y2pmbuild and suse-update sources
by David Keller 13 Aug '06

13 Aug '06

Hello, I just made my first experience with y2pmbuild and packed some applications and libraries. All worked fine. Yet I would like to pack a kernel-module and later install it on my system. Through yast online-update I managed to have kernel-2.6.16.21 installed on my box. But when I try to build the module with y2pmbuild I get an rpm-file which is built on kernel-2.6.16.13. My dists_common file looks like this: ****snip***** # additional sources, specify with url_... add_sources="suse susenonoss" # suse here is the one from $add_sources url_suse="http://mirror.switch.ch/ftp/mirror/opensuse/distribution/SL-10.1/inst-sourc…" url_susenonoss="http://mirror.switch.ch/ftp/mirror/opensuse/distribution/SL-10.1/non-oss-in…" url_suseupdate="http://mirror.switch.ch/ftp/pub/suse/update/10.1" *****snip***** Don't care about the hard-coded version in the sources yet (I know how to replace it with a more general formulation, but had no need to do it so far). Seemingly it is not possible to add the source suseupdate by replacing the add_sources-tag with add_sources="suse susenonoss suseupdate". This results in a lot of unresolved conflicts in the initialization of y2pmbuild. Does somebody know a workaround? Thanks in advance Regards David Keller

2 3