Nice, thanks. A minor nitpicks inline … Le mardi, 23 octobre 2018, 21.28:40 h CEST Tollef Fog Heen a écrit : > === DRAFT Resolution === > > Vendor-specific patch series are a feature of dpkg that can be used to > apply a different series of quilt patches when the source package is > unpacked on different systems. Since Debian source packages are usually > treated as a pure transport format (like tar), this property can cause > confusion and frustration for users. Examples could be if only the > series file for one vendor is updated, or a source package is unpacked > on one system and then transferred to a system with a different vendor > for debugging. > > The Committee recognises that there is a need for packages to behave > differently when built on different distributions, but this should be > done by using different source packages, or as part of the build > process, using current and future practices such as patches with > conditional behaviour, patching of files during the build, rather than -----------------------^ use "or", as the list of examples has only two items? > at source unpacking time. > > Since this feature is used by several packages today, we need a > reasonable transition period. They will be considered buggy from when > this resolution is accepted, but it will not be considered severe enough > to warrant immediate removal from Debian. After Buster is released, the > presence of a vender-specific patch series will be a violation of a MUST --------------------^ vendor > directive in Debian policy. > > The Committee therefore resolves that: > > 1. Any use of dpkg's vendor-specific patch series feature is a bug for > packages in the Debian archive (including contrib and non-free). > > (…) > > 2. After Buster is released, use of the vendor-specific patch series > feature is forbidden in the Debian archive. > > (…) I'm not sure how these are to be interpreted with regards to "the whole Debian archive" vs "unstable". I'd adopt a more Policy-like language like: > 2. After Buster is released, packages must not use vendor-specific patch > series. … but it resonates with the second paragraphs. I can live with the existing phrasing. Cheers, OdyX
Attachment:
signature.asc
Description: This is a digitally signed message part.