| 1 |
>emerge --changelog ? |
| 2 |
> |
| 3 |
> |
| 4 |
k, sorry :) |
| 5 |
|
| 6 |
>This should go to gentoo-dev@g.o as ebuild developers are the ones that decide |
| 7 |
>what USE flags are available and how they're documented. |
| 8 |
> |
| 9 |
> |
| 10 |
Of course they decide what flags are available, but how do they decide |
| 11 |
how they are documented? I'm sorry if i did not yet discover gentoos |
| 12 |
ebuild-feature-documentation system. |
| 13 |
|
| 14 |
I thought of a command like emerge mozilla-firefox --useinfo |
| 15 |
that prints what each flag is good for. Maybe some are explained in 5 |
| 16 |
words, other may need 5 lines. |
| 17 |
|
| 18 |
>>also, the advanced could provide |
| 19 |
>>- links to howto's (like configuring apache) |
| 20 |
>> |
| 21 |
>> |
| 22 |
> |
| 23 |
>This is out of the domain of a package in any package management system IMO. |
| 24 |
> |
| 25 |
> |
| 26 |
You are right, there may be no pms out there that has this feature. |
| 27 |
I refuse to accept this as an argument to not change that. |
| 28 |
You may be a pro who does not need any HOWTOs, i am not. |
| 29 |
Portage saves a lot of work for people who use it. But in some cases, |
| 30 |
ebuilds don't do everything they could or should. |
| 31 |
Example: Firefox and Thunderbird don't give a damn on the LANG setting, |
| 32 |
they are english by default. There is no obvious way to change the |
| 33 |
language, you need to do some investigation. (Look for the HOWTO ;) ) |
| 34 |
|
| 35 |
BTW, if "This is out of the domain of a package in any package |
| 36 |
management system", then why do some packages print additional |
| 37 |
information after emerging, like what files should be updated manually? |
| 38 |
THIS is not really the solution. if you batch-emerge or the package that |
| 39 |
wants to tell you something is just a dependancy, then you may probably |
| 40 |
miss that note. |
| 41 |
|
| 42 |
Another reason to inform the user before emerging maybe this: |
| 43 |
I emerged a package recently, think it was amule, that first emerged |
| 44 |
some dependancies, including wxGTK. |
| 45 |
Then, after all dependancies were emerged, the package itself quitted |
| 46 |
saying that wxGTK needs to be emerged with flag wxgtk1. |
| 47 |
I thought the ebuild could manage flags of dependancies automatically, |
| 48 |
but that is not the point. |
| 49 |
The user could be informed before starting to emerge. |
| 50 |
|
| 51 |
>>- list packages that are of use for this (plugins or utilized apps like |
| 52 |
>>cervisia that integrates in quanta plus) |
| 53 |
>> |
| 54 |
>> |
| 55 |
> |
| 56 |
>Do you mean finding packages that depend on that package in question? |
| 57 |
> |
| 58 |
> |
| 59 |
Not necessarily. Cervisia, Kompare and Tidy are standalone applications, |
| 60 |
but Quanta integrates them automatically if they are installed. |
| 61 |
|
| 62 |
>>- tell how to contact the ebuild maintainer |
| 63 |
>> |
| 64 |
>> |
| 65 |
> |
| 66 |
>metadata.xml. This information is printed out when using -vv in |
| 67 |
>portage-2.1_alpha. |
| 68 |
> |
| 69 |
> |
| 70 |
Hey, thats cool :) |
| 71 |
But then, why not include additional information there? like the useflag |
| 72 |
documentation or links to HOWTOs? |
| 73 |
|
| 74 |
>Personally, I hate most wikis. 9 times out of 10, they are full of |
| 75 |
>half-correct information. This makes them all the more dangerous as the |
| 76 |
>"average Joe" can't tell what's correct and what isn't. |
| 77 |
> |
| 78 |
> |
| 79 |
My wiki experiences are all good, but i also wrote, that it could only |
| 80 |
be maintained by the developers. Only the discussion page attached to |
| 81 |
each page is open for comments. This also prevents defacements. |
| 82 |
|
| 83 |
>Ideas are "a dime, a dozen". |
| 84 |
> |
| 85 |
> |
| 86 |
Ideas are even free. That's what makes open source what it is. |
| 87 |
Ask Bryce Harrington what he thinks how Inkscape's well development is |
| 88 |
related to its community. |
| 89 |
|
| 90 |
Caliga |
| 91 |
-- |
| 92 |
gentoo-portage-dev@g.o mailing list |
Archives