[opensuse-packaging] Splitting up splashy, circular dependency
Hi, I need to split of branding packages from splashy: splashy-branding-upstream splashy-branding-openSUSE splashy-branding-SLED The core splashy package requires a branding package to be functional. However, the splashy-branding packages need a tool (splashy_config) to set the actual theme when installed (%post), which is in the core splashy package. So, does anyone has a hint how to solve this? Thanks, Holger -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi,
I need to split of branding packages from splashy:
splashy-branding-upstream splashy-branding-openSUSE splashy-branding-SLED
The core splashy package requires a branding package to be functional. However, the splashy-branding packages need a tool (splashy_config) to set the actual theme when installed (%post), which is in the core splashy package.
So, does anyone has a hint how to solve this? why do you have to split off the "upstream" branding as well. If you keep that in the main package (as subpackage) then
On Monday 03 November 2008 13:56:32 Holger Macht wrote: the tool has it's branding package as fallback and the other ones can build on top of the main package. -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de) ---------------------------------------------------------------------- Linux MacBookRudi 2.6.27.4-2-default #1 SMP 2008-10-28 22:32:39 +0100 x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Tue 04. Nov - 01:40:45, Ruediger Oertel wrote:
Hi,
I need to split of branding packages from splashy:
splashy-branding-upstream splashy-branding-openSUSE splashy-branding-SLED
The core splashy package requires a branding package to be functional. However, the splashy-branding packages need a tool (splashy_config) to set the actual theme when installed (%post), which is in the core splashy package.
So, does anyone has a hint how to solve this? why do you have to split off the "upstream" branding as well. If you keep that in the main package (as subpackage) then
On Monday 03 November 2008 13:56:32 Holger Macht wrote: the tool has it's branding package as fallback and the other ones can build on top of the main package.
Right, that would be a solution. I just wanted to split it because several other branding packages are using this -upstream policy. Regards, Holger -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Holger Macht schrieb:
I need to split of branding packages from splashy:
splashy-branding-upstream splashy-branding-openSUSE splashy-branding-SLED
The core splashy package requires a branding package to be functional. However, the splashy-branding packages need a tool (splashy_config) to set the actual theme when installed (%post), which is in the core splashy package.
So, does anyone has a hint how to solve this?
I would do it the other way around. I would rename the original splashy package to splashy-core. The branding packages should require this one and all branding packages should have a provides tag for splashy. Herbert -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Tue 04. Nov - 10:14:17, Herbert Graeber wrote:
Holger Macht schrieb:
I need to split of branding packages from splashy:
splashy-branding-upstream splashy-branding-openSUSE splashy-branding-SLED
The core splashy package requires a branding package to be functional. However, the splashy-branding packages need a tool (splashy_config) to set the actual theme when installed (%post), which is in the core splashy package.
So, does anyone has a hint how to solve this?
I would do it the other way around. I would rename the original splashy package to splashy-core. The branding packages should require this one and all branding packages should have a provides tag for splashy.
Hm, another good solution. Thanks. Now I have the choice. Thanks, Holger -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (3)
-
Herbert Graeber -
Holger Macht -
Ruediger Oertel