| 1 |
>>>>> On Tue, 05 Oct 2021, Michał Górny wrote: |
| 2 |
|
| 3 |
> On Tue, 2021-10-05 at 19:27 +0100, Sam James wrote: |
| 4 |
>> This is a preliminary version/draft of a proposed change to |
| 5 |
>> GLEP 68. |
| 6 |
>> |
| 7 |
>> I'd like to introduce a method for developers to signal anything |
| 8 |
>> special about a package and how to correctly maintain it. |
| 9 |
>> |
| 10 |
>> Sam James (1): |
| 11 |
>> glep-0068: Add notes element for package maintenance instructions |
| 12 |
>> |
| 13 |
>> glep-0068.rst | 26 +++++++++++++++++++++++--- |
| 14 |
>> 1 file changed, 23 insertions(+), 3 deletions(-) |
| 15 |
|
| 16 |
> To be honest, I don't think adding it to metadata.xml is a good idea. |
| 17 |
> This is not something that's going to be machine-parseable, |
| 18 |
> and expecting people to look into metadata.xml to see if it's even |
| 19 |
> present is a bit much. |
| 20 |
|
| 21 |
The same argument would apply to longdescription. |
| 22 |
|
| 23 |
> Maybe we could just add README files to the package directories |
| 24 |
> in question. This would have the clear advantage that the files will be |
| 25 |
> immediately visible. |
| 26 |
|
| 27 |
Scattering a package's metadata across multiple files doesn't look like |
| 28 |
a good idea to me. |
| 29 |
|
| 30 |
Ulrich |
Archives