Re: Bug#286214: ITP: kwin-style-asteroid -- Pixel-for-pixel clone of Win2000 GUI style for KDE
Le vendredi 18 février 2005 à 12:35 +0100, Marcin Orlowski a écrit :
> It enforces you to fetch and install 9 additional components you simply
> do not want. Going that way, why do not put i.e. all the PHP modules in
> one deb? or even better - we shall have it all with apache. or even better
> we shall have one big "webserver" package with all the stuff related.
> Got the point?
You have to find a good balance between putting everything in a single
package and putting every random file in a separate package.
> > And if it does, there's nothing stopping you from updating the package,
> > say, every three months (unless there's a critical bug in one of the
> > themes), is there?
> The thing I don't like in debian is that it usually stays far behind
> in term of updating packages. I often hear "Debian? no, I want be up
> to date".
Hey, we're talking about kwin themes. Not stuff that gets updated every
> Why do you imitate you care modem users? You care a few bytes more in
> Packages (text file! gzipped!) but ommit additional megabytes in the
> package? It's like promoting bloatware ;)
No, this is promoting clarity in our packages listing. Users will get
lost if they have to install separate packages for things as trivial as
Our GDM themes are all in a single package; do you think it would do any
good to separate them, only to save 1 MB of download? Our users would be
lost; there's no way you can tell which GDM theme you want before having
seen what they look like. It's exactly the same for kwin themes: if the
user wants a specific theme, having a special package for it is almost
no gain, as the user can download the theme and install it in a few
seconds. If you don't know what theme you want, you'll have to install
all of them and test them. That's when a single package becomes handy.
.''`. Josselin Mouette /\./\
: :' : firstname.lastname@example.org
`. `' email@example.com
`- Debian GNU/Linux -- The power of freedom