On Sun, Jul 24, 2011 at 5:56 AM, Rex Dieter <span dir="ltr"><<a href="mailto:rdieter@math.unl.edu">rdieter@math.unl.edu</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> 1. Use an empty "meta" package that pulls in a default (gtk) front end. E.g<br>
> :<br>
> Pname (meta) -> Pname-common -> Pname-gtk<br>
> Pname-gtk -> Pname-common and<br>
> Pname-qt -> Pname-gtk<br>
><br>
> Or,<br>
><br>
> 2. Create sub packages for each front end, i.e *-gtk and *-qt, that depend<br>
> on a common package. So :<br>
><br>
> Pname-gtk -> Pname<br>
> Pname-qt -> Pname<br>
<br>
</div>either is fine. 1 is just a variant of 2 with the addition of the metapackage really,<br>
which I personally consider not necessary, but I also consider it something left to the<br>
discretion of the maintainer in question.<br></blockquote><div><br>Great -- I've already done the packaging as per 1 (by looking at transmission). <br><br>I feel the meta package approach is better, because users can run "yum install Pname", <br>
and get the Gtk bits. The only issue is for Qt users, as they will have to search and<br>understand to use "yum install Pname-qt", to pull in the correct front end.<br><br>If I'm not mistaken, .deb uses meta packages to do this as well.<br>
<br>Thanks,<br><br>-- Raghu<br></div></div>