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