| 1 |
Hi, |
| 2 |
|
| 3 |
Daniel Stiefelmaier wrote: |
| 4 |
>> Take the USE flag "perl", for example. It has the description "Adds |
| 5 |
>> support/bindings for the Perl language." but for mysql setting it |
| 6 |
>> enables the installation of some support scripts that just happen to |
| 7 |
>> be written in perl. |
| 8 |
|
| 9 |
Since perl is a global use flag, this is inappropriate use. You might want to |
| 10 |
file a bug :) |
| 11 |
|
| 12 |
> man emerge provides information on possible options, why should there |
| 13 |
> not be a way to get information on an ebuilds option??? |
| 14 |
|
| 15 |
because emerge is the tool, not the object. You wouldn't expect the openoffice |
| 16 |
documentation to cover examples for different kinds of letters, would you? |
| 17 |
|
| 18 |
> The useflag "xprint" sounds like printing support, but doesn't tell if |
| 19 |
> you need it if you use cups or the kde-printing system or... whatever. |
| 20 |
|
| 21 |
~ $ grep xprint /usr/portage/profiles/use.desc |
| 22 |
xprint - Support for xprint, http://www.mozilla.org/projects/xprint/ |
| 23 |
|
| 24 |
what do you need more? |
| 25 |
|
| 26 |
> - There are many Gentoo-related HOWTOs, not linked on a projects homepage |
| 27 |
|
| 28 |
You can easily find those through searching google |
| 29 |
|
| 30 |
> - Some ebuilds give homepages like "gnome.org" just for some little |
| 31 |
> gnome app that is not linked on gnome.org |
| 32 |
|
| 33 |
Same here, googling usually helps |
| 34 |
|
| 35 |
> - There are not only howtos but other useful related pages |
| 36 |
|
| 37 |
Same here. |
| 38 |
|
| 39 |
> Why do you think just because YOU don't need it, noone will? |
| 40 |
|
| 41 |
This is not a personal debate. The most important reason I see against this idea |
| 42 |
is that portage is a package manager, not a documentation center. |
| 43 |
|
| 44 |
Why should the ebuild contain links to documentation? To be honest, not even the |
| 45 |
HOMEPAGE info is needed, it's just for the user's convenience. I tend to refer |
| 46 |
to the UNIX principle: The right tool for the right job. For your problem, |
| 47 |
google (or any other search engine of course) is the right tool. |
| 48 |
|
| 49 |
> No, don't give information to users! Don't have a defined way to get |
| 50 |
> information to a package! It's evil! |
| 51 |
|
| 52 |
Do you think we're all sadists? Sorry, but such statements don't help your |
| 53 |
argumentation. |
| 54 |
|
| 55 |
>>> BTW, if "This is out of the domain of a package in any package |
| 56 |
>>> management system", then why do some packages print additional |
| 57 |
>>> information after emerging, like what files should be updated manually? |
| 58 |
|
| 59 |
For the user's convenience of course. Introducing documentation links in ebuilds |
| 60 |
however is a massive effort, and I don't think that effort is worth it. I'd |
| 61 |
rather fix a broken package than googling for documentation. |
| 62 |
|
| 63 |
I'm sure every user is able to search for HOWTOs, but not every user is able to |
| 64 |
fix a broken package himself. |
| 65 |
|
| 66 |
> That question was rhetorical. Of course it's because portage can't |
| 67 |
> handle everything. |
| 68 |
> This is why there should be an easy, defined way to get information. |
| 69 |
|
| 70 |
This defined way is google, IMHO. |
| 71 |
|
| 72 |
Regards, |
| 73 |
|
| 74 |
-- |
| 75 |
Simon Stelling |
| 76 |
Gentoo/AMD64 Operational Co-Lead |
| 77 |
blubb@g.o |
| 78 |
-- |
| 79 |
gentoo-portage-dev@g.o mailing list |
Archives