On 30 June 2011 12:30, jdd
Le 30/06/2011 12:25, Rob OpenSuSE a écrit :
On 30 June 2011 09:24, jdd
wrote: isn't that what Pattern are used for? kde pattern, gnome pattern...
I think Patterns select a group of packages that tend to be used together, like KDE4 Desktop, or LAMP server; which is a very different purpose.
you can create any kind of pattern (AFAIk), and there are default selected package in pattern and also non default selected ones.
That's interesting, patterns would seem basically lists of packages then, that are in effect "tagging". There's Package groups to, which seem smilar only without the "Intall" options. However the Software Manager only has a very limited browsing & selection on patterns at present, there's no simple way either for the end user to add their own tags to reuse later.
the problem of your system tags is that this needs to be manually tagged. or is it possible in OBS to ask maintainers to clik in a tag list?
Very definitely but as I understood it, this was an ideas and
requirements discussion, for something that would need development,
perhaps I misunderstood. I really hate a restricted hierarchy for
organisation, for problems mentioned. Altering package names would be
impractical; and once we consider additional repos likely to be
unworkeable. Nevermind that using the name to signal attributes, will
limit the info's presentation eg) fixed alphabetic sort order of name,
rather than Function, Implementation Technology, Philosophy Features v
Compactness which become doable in a more general framework.
Browsers offer "Tags" for Book Marks & web applications like Gmail
have "Labels", so it seems like a fairly common DataBase type
application, with extensions needed to browse & generate queries in
the Software Catalogue. There must be code around already, that
perhaps could be recycled and integrated?
Perhaps the community could help create the information, outside of
the package build system; rather than all of the categorisations being
another task for package maintainer's to complete.
On 28 June 2011 14:14, Ilya Chernykh
I first discussed this issue with coolo in private but possible a wider range of ideas may be beneficial.
All of us know that is is sometimes confusing to find a package which belongs to your desktop environment, whether Gnome or KDE. Sometimes you have to look into package's dependencies to find out whether it is written in GTK or Qt.
As the number of desktops increases, the problem only becomes worser.
Currently the packages are classifies using the RPM groups. But for the most packages this groupping only reflects the package's purpose, i.e. network, game or office. This groupping is organized as a tree, and there is no possibility to add another categorization.
An obvious solution is to add a desktop environment name to the package's name such as prefixing all KDE apps with "kde-" or simple "k". But this is also confusing and may require much of work as renaming is not an easy task.
So are there any ideas on how to organize this better?
Well I really think package renaming, won't solve the problem for end users, who want to select a package based on rational criteria, to find what suits them. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org