| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 01/07/2013 11:46 AM, Amadeusz Żołnowski wrote: |
| 5 |
> Hi, |
| 6 |
> |
| 7 |
> Quoting Pacho Ramos (2013-01-07 10:34:52) |
| 8 |
>> - Eclass was originally oriented to cover those kind of messages |
| 9 |
>> that could be shown by elog first time the package is merged and, |
| 10 |
>> later, rely on people reading that README.gentoo |
| 11 |
> |
| 12 |
> This would be good - show README.gentoo for first time, and treat |
| 13 |
> it with config-protect (as Duncan said somewhere) to be sure user |
| 14 |
> is not going to miss changes (which could be compared with |
| 15 |
> dispatch-conf). |
| 16 |
|
| 17 |
Maybe something similar to CONFIG_PROTECT is desirable, but it's not |
| 18 |
exactly the same. The main differences are that the user will always |
| 19 |
want to accept changes to README.gentoo, and the user will not be |
| 20 |
interested in trivial formatting changes to README.gentoo. If |
| 21 |
README.gentoo contained a version number that the package manager |
| 22 |
could parse, then the package manager could detect when the version |
| 23 |
number is bumped (indicating a non-trivial change). |
| 24 |
- -- |
| 25 |
Thanks, |
| 26 |
Zac |
| 27 |
-----BEGIN PGP SIGNATURE----- |
| 28 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 29 |
Comment: Using GnuPG with undefined - http://www.enigmail.net/ |
| 30 |
|
| 31 |
iEYEARECAAYFAlDrc5IACgkQ/ejvha5XGaNPTACg1w1FGrSm+JAG4otnmRT5iIvu |
| 32 |
DycAoPLCmR8223UH7zzD4HfQ7TiRJWQs |
| 33 |
=idLH |
| 34 |
-----END PGP SIGNATURE----- |
Archives