[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#632655: ITA: conky -- highly configurable system monitor



On Wed, Jul 13, 2011 at 12:23 PM, Francesco Poli
<invernomuto@paranoici.org> wrote:
> On Tue, 12 Jul 2011 12:16:30 -0700 Vincent Cheng wrote:
>
>> retitle 632655 ITA: conky -- highly configurable system monitor
>> owner 632655 Vincentc1208@gmail.com
>> thanks
>
> Hello Vincent!
>
> I am very happy to see that you decided to adopt conky.
> Even more happy to see how quickly you came to the rescue!
> Thanks a lot for your willing to help!
>
> I really hope that you manage to adopt it soon and that you are willing
> to move it back to the main archive, by disabling the nvidia support
> (see bug #579102 for the details).
>
> Once again, many thanks for your intention to help out.
>
> Bye.
>
> --
>  http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
>  New GnuPG key, see the transition document!
> ..................................................... Francesco Poli .
>  GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE
>

Hi Francesco,

As a longtime Conky (and Debian) user, I'm definitely willing to make
sure that Conky is properly maintained in Debian. :)

I've taken a close look at #579102 and the various ways this issue can
be fixed, I'm inclined to go with a different method altogether; have
a source package "conky" that provides "conky-cli" and "conky-std"
binaries (and the transitional "conky" package), both compiled without
the --enable-nvidia flag (so it can be moved to main), as well as a
new source package named "conky-all" that provides a "conky-all"
binary, with Nvidia support (the status quo; this would go in
contrib). The transitional "conky" package would depend on conky-all |
conky-std (currently it only depends on conky-all), so Debian users
with contrib enabled would install the former, and those without
contrib would install the latter. If you want a comparison, I suppose
this is somewhat similar to how p7zip and p7zip-rar are packaged.

Why am I seemingly making this more complicated? Well, for one thing,
I personally use the binary Nvidia blob, so I would prefer not to have
Nvidia support disabled in Conky. However, I understand why it would
be preferable to have Conky in main rather than contrib, and I respect
users who don't want to have contrib or non-free enabled in their
sources.list. I've also taken a look at Raphael Hertzog's blog post
about having different dependencies for the same package synced
between Debian and Ubuntu, but that would mean that Debian users would
no longer have the option of installing a Conky package with Nvidia
support enabled (I don't think that Ubuntu users are the only ones who
want this feature). With my solution, Debian users can still install
Conky without the need for contrib, yet they also have the option to
install a Conky compiled with --enable-nvidia, if they want to; Ubuntu
users would not notice any difference.

I'd gladly welcome any comments or suggestions.

Kind regards,
- Vincent Cheng



Reply to: