[Bug 209260] Review Request: beryl-manager - Beryl window decorator and theme management utility

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: beryl-manager -  Beryl window decorator and theme management utility


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209260





------- Additional Comments From jwilson at redhat.com  2006-11-14 17:21 EST -------
(In reply to comment #9)
> Package looks almost well.
> I haven't checked the another beryl packages yet, but you
> use Provides: beryl in beryl-core package and here you're using
> Requires: beryl-core. Maybe Requires: beryl would be better?

I'm thinking stick with beryl-core in the sub-packages, for the reason below...

> And the another thing: if a normal user type `yum install beryl`,
> he won't get working beryl environment. He'll get only a beryl-core
> package which alone is useless. Maybe you should create dependencies
> differently to make possibility to install all essential beryl packages
> by simply typying `yum install beryl`? How do you think?

I initially did Provides: beryl in beryl-core because it seemed right at the
time. It did cross my mind the other day to perhaps switch to a beryl
meta-package that Requires: all the beryl components. Only downside with that is
that it can suck in a fair amount of stuff now that people may not want if
they're running one desktop or another (i.e. kde vs. gnome, where aquamarine
Requires: some kde stuff, heliodor Requires: some gnome stuff). Could do three
meta-packages, beryl, which in turn Requires: beryl-kde and beryl-gnome, which
in turn Requires: packages appropriately for each DE.

Some scheme along these lines definitely seems better than beryl-core Provides:
beryl, which does indeed provide nothing of use in the case of a user yum
installing only beryl.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.