RFS: gnome-shell-extensions

Victor Seva linuxmaniac at torreviejawireless.org
Sun Nov 6 13:57:54 UTC 2011


2011/11/6 Leo 'costela' Antunes <costela at debian.org>:
> On 06/11/11 12:34, Josselin Mouette wrote:
>> Since there is no extension manager in 3.0, I think we should start this
>> package from gnome-shell 3.2 (currently sitting in experimental). This
>> way there would be no need for this hair-splitting
>> one-extension-per-package which only makes things more complicated.
>
> I imagine you probably heard this question a thousand times already, but
> do you have a rough time-frame for 3.2 entering unstable?
> If it's still months away, I'd suggest uploading it as-is now, because
> IMHO its usefulness outweighs the slight annoyance of having to manually
> disable the unwanted extensions after installing (and I imagine we're
> only talking about sid/testing here, as the released version will
> probably be ">= 3.2").

Yes, I think if the time frame is long as months, we can start with this
one-extension-per-package. I think our users would like so.

>> Let’s just select a default set of extensions useful to enable by
>> default (at least alternative-status-menu) and this should be much
>> better.
>
> User-theme might also be a good candidate, since it's unintrusive and
> gnome-tweak-tool already expects to find it.

I have a first draft of 3.2.0-1 with just one package at [0]. But I don't follow
both of you. How can I select which extensions have to be loaded by default?

[0] https://github.com/linuxmaniac/pkg_gnome-shell-extensions

Thanks.



More information about the pkg-gnome-maintainers mailing list