[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#914383: debian-policy: re-encode virtual package list in YAML



Thank you all for your encouragement!

On Thu, Nov 22, 2018 at 06:29:19PM -0700, Sean Whitton wrote:
I have not thought through Bill's arguments here carefully, but let's
not block making the list of virtual packages machine-parseable on the
question of whether or not we can remove the changelog.

Let's just retain the changelog in a YAML comment, and proceed to merge
the conversion to a machine-parseable format.

Agreed: let's not block on the changelog at this point, further
discussion is needed. Ive re-instated the changelog in the form of a
YAML comment and rebased my branch in Salsa (so the branch URI from my
initial mail is still valid but that commit URI is now out of date)

I'm hesitant to over-burden this initial patch with too much stuff, but
with the prospect of future YAML schema changes, I felt it best to bake
in a "schemaVersion" right from the off, so I've done that too.

I have written a simple tool in Python to validate against the schema
but I have not included it in this PR. It's here:
<https://salsa.debian.org/jmtd/policy/commits/structure-vpkg-tools>

I realise the other tooling in policy is written in perl. A putative
perl version of the tool is included in that other branch, but it does
not yet work (I need to wake up my perl brain cells and remember how to
use hash references properly)

On Thu 22 Nov 2018 at 10:17PM +0100, Bill Allombert wrote:
The changelog could be kept as comment in the YAML file, or maybe better,
the adoption and deprecation date could be simply added to the YAML
data (but this require adding back the obsolete packages to the list).
This way this would be machine readable too.

The document contains an (empty) section immediately before the
ChangeLog "Old and obsolete virtual package names" for this purpose
(that I had initially stripped with the ChangeLog and have now
restored).

To bring it back into use, I agree it would be better to re-encode it
into the YAML structure, but I defer that for a future time.


Best wishes

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄⠀⠀⠀⠀


Reply to: