| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 01/12/2013 02:34 AM, Pacho Ramos wrote: |
| 5 |
> El sáb, 12-01-2013 a las 02:01 -0800, Zac Medico escribió: |
| 6 |
>> On 01/12/2013 01:46 AM, Pacho Ramos wrote: |
| 7 |
>>> El mié, 09-01-2013 a las 12:04 -0800, Zac Medico escribió: |
| 8 |
>>>> On 01/09/2013 11:53 AM, Pacho Ramos wrote: |
| 9 |
>>>>> This changes the name of eclass to readme.gentoo.eclass and |
| 10 |
>>>>> gets information from ${FILESDIR}/README.gentoo |
| 11 |
>>>> |
| 12 |
>>>> What if there are multiple versions/slots that have |
| 13 |
>>>> different README.gentoo content? Maybe the eclass should |
| 14 |
>>>> accommodate that somehow? |
| 15 |
>>> |
| 16 |
>>> This should work, it will read DOC_CONTENTS variable from |
| 17 |
>>> ebuild and, if not set, rely on common |
| 18 |
>>> ${FILESDIR}/README.gentoo |
| 19 |
>> |
| 20 |
>> You might add a loop to search for a version-specific |
| 21 |
>> README.gentoo, like this: |
| 22 |
>> |
| 23 |
>> file= for suffix in -${PV} -${PV}-${PR} "" ; do [[ -f |
| 24 |
>> ${FILESDIR}/README.gentoo${suffix} ]] && \ |
| 25 |
>> file=${FILESDIR}/README.gentoo${suffix} && break done if [[ |
| 26 |
>> ${file} ]] ; then cp "${file}" "${T}"/README.gentoo dodoc |
| 27 |
>> "${T}"/README.gentoo fi |
| 28 |
>> |
| 29 |
> |
| 30 |
> Thank for explaining me how to do that. The problem is that I doubt |
| 31 |
> if it would really be useful as we usually won't need whan |
| 32 |
> README.gentoo per version, only to update if for some special cases |
| 33 |
> from time to time :/ |
| 34 |
> |
| 35 |
> For example: foo-1.0 relies on common README.gentoo file, foo-1.1 |
| 36 |
> adds new feature and, then, would use README.gentoo-1.1 file... but |
| 37 |
> foo-1.2 will probably use the same README.gentoo-1.1 file :| |
| 38 |
|
| 39 |
Still, it maybe it would be reasonable to use a different |
| 40 |
README.gentoo for each SLOT, it there's more than one? Maybe it makes |
| 41 |
more sense to have another variable like DOC_CONTENTS, but have it |
| 42 |
refer to a filename? Then you should have multiple revisions of an |
| 43 |
ebuild refer to the same file, without having to have duplicate |
| 44 |
CONTENTS settings. |
| 45 |
- -- |
| 46 |
Thanks, |
| 47 |
Zac |
| 48 |
-----BEGIN PGP SIGNATURE----- |
| 49 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 50 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 51 |
|
| 52 |
iEYEARECAAYFAlDxW8oACgkQ/ejvha5XGaNc+wCgiaOC7oLLxRvgrGIO9t4SbqTN |
| 53 |
Vw8AoIx88SBpcrHAcBO9HhQaCyrtEf3A |
| 54 |
=cHLC |
| 55 |
-----END PGP SIGNATURE----- |
Archives