[Bug 82451] [fr] French translation for the kde-split-ebuild.xml documentation

[email protected]
Newsgroups gmane.linux.gentoo.documentation.french
Message-ID <[email protected]>
http://bugs.gentoo.org/show_bug.cgi?id=82451


[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]




------- Additional Comments From [email protected]  2005-02-18 06:05 PST -------
Clement emailed me; CCing kde team.

The first of the two FAQ items (how to unmerge an older KDE) should indeed be
handled by portage functionality. Specifically, GLEP 21 (package sets). meta
ebuilds should be replaced by sets.

I could write about GLEP 21 in the FAQ, but that wouldn't help non-geek users
like your mother. This issue isn't specific to kde; gnome 1.4/2.x has different
SLOTs too. KDE does have more ebuilds involved than any other case such as
gnome, but even gnome's several dozen ebuilds (which aren't all in one dir)
are a pain to uninstall manually. The user also has to know enough about
ebuilds to understand the concept of unmerging a slotted ebuild version. IMHO
that's on the same level of skill/knowledge as running the sample script given
in the FAQ. Would it help if that script was packaged nicely and available
through an ebuild? (gentoolkit? But that might require the script to have more
general application...)

The second FAQ item's answer is aimed at people writing a script to begin with.
It's true that I don't normally separate such people from those 'merely' using
a shell :-) Would it help to give here, also, a sample shell command that
would output the list of ebuilds inheriting from a given parent package?
I don't see what more can be done.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


--
[email protected] mailing list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.