On Friday 13 March 2009 07:40:46 am Lukas Ocilka wrote:
Carlos E. R. wrote:
On Friday, 2009-03-13 at 08:28 +0100, Jiri Srain
wrote:
Good
idea. Also popularity will give a guide as to where the most
testing
& integration effort should be focussed - the bits which are most
popular
must also be the most reliable and best integrated.
This idea is great, bus misses one more information: How often is the
backage
being used, or, more simply, has it been used at all, or was it
installed just
as a part of a pattern, or a newbie installed simply everything just
in case
it will be needed?
Then use the accounting in Linux to track which apps the user is running
and use cron to feed that info automatically to a server.
Hi,
As you probably know, we were talking about this during or
"BrainStorming Prague" and a solution has been proposed: use popcon (or
something similar)
http://tinyurl.com/suse-popcon
https://features.opensuse.org/305877
Popco(r)n should solve more than just only "installed packages" but also
"how often are these packages/application" used (and more).
Bye
L.
The main idea is not statistics what packages are used.
That part we can already have by reading
http://popcorn.debian.org .
They have Linux packages too ;-)
Popcorn can help to set priorities on maintenance and what to include on
delivered media, to have minimal media and minimal download. DVD is fine, but
80% of users never touch some programs.
What Popcorn is not designed to solve is package selection for particular
purpose. Some not so popular packages can be valuable in some not so often
used configuration.
Main idea was to create place where users that are skilled in configuration of
the system, or parts of it, can share their config files. Initially I thought
only about exporting list of installed packages, but you can publish any
config file you want. Repository selection for instance.
Imagine, that someone wants minimal system. He/she spend time configuring that
and finally come to something that is usefull. As it is now, he is happy
camper, but another person has to do the same for his computer, and so on.
Not everyone is skilled in configuration business, so good minimal, or secure,
or funny, or educational, or name it, system is not reachable to everyone.
For the part of openSUSE that is on Novell payroll is not viable to maintain
endless variations. If users can exchange config files, they can go and find
one that fits their ideas, add few pieces and be fine.
Advantage:
It will allow reuse of knowledge and fine control of installation process that
is not possible right now.
It will prevent endless discussions on topic what should be in default system.
It will help developers to select most popular mix of packages, instead to
guess.
Whole voting procedure about best mix of packages is no more on mail list, it
is on server that will have configurations.
Example:
You don't like desktop effects and few more features, because your computer is
old and slow, you remove packages that make it slow, and publish you version.
If someone complains about the same, point to "no desktop effects" selection
of packages. Download, import, check what YaST wants to do, and Accept, or
Cancel.
Disadvantage:
Currently you can export or import whole selection, there is no way, without
external tools, to add or subtract few packages.
Using rpm to do the same is sort of magic, far from simple, and that limits
ability of many people that have other skills to participate.
Thoughts?
--
Regards, Rajko
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org