Hello, Am Sonntag, 2. September 2012 schrieb Karl Ove Hufthammer:
I also have another packaging question for the application. The main application is an architecture-independent command-line shell script, but it also has an optinal KDE-based GUI (actually, a plasmoid), not currently packaged.
The original package works fine as a command-line application, and I don’t want any unneeded dependencies on KDE. So I guess for the GUI part I should create a *new* package, with a new .spec file, with a ‘Requires’ line depending on the needed KDE packages and the command-line package (it uses the shell script and the data files). Is that correct, or can everything be written in *one* .spec file? And if I create a new package, is it possible for this to somehow use the original source tarball, so I don’t have to upload it twice every time a new version is released?
If the code for the GUI comes from the same tarball, the usual way is to build a sub-package from the same spec. You'll need something like %package gui Summary: GUI for [...] Requires: kde4-something [...] %description gui Long description of the gui subpackage %files gui [...] The only restriction is: if the main package is noarch, subpackages can't be arch-specific AFAIK.
BTW, the KDE-based GUI is actually written in Python, and contains binary executables, so I guess this should be ‘noarch’ too?
With the added "contains NO binary executeables" it probably can be noarch. Regards, Christian Boltz -- +++ vcdimager.changes +Thu Apr 7 15:49:40 UTC 2011 - jw[at]novell.com [...] +- new copyright patch added, to fulfill Joerg's last wish in bnc#672491 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org