On Sun, 2020-05-24 at 01:23 +0100, Ben Hutchings wrote: > I'm going to talk about this at MiniDebConf Online next week, but since > I'm developing it with some of the kernel team's packages in mind I > thought I would give some advance notice here. Something I forgot to mention is that this depends on jinja-vanish, which is currently in the NEW queue. My packaging repo for that is at: https://salsa.debian.org/benh/jinja-vanish Ben. > This is currently under my personal namespace on Salsa: > https://salsa.debian.org/benh/debplate > > I've just updated the README file to document (hopefully) all the > features that currently work. There's also a TODO list with all of the > things I think still need to be done for a v1.0. > > There are some examples in the debplate source. I have a work-in- > progress conversion of firmware-nonfree to use debplate, which is at: > https://salsa.debian.org/benh/firmware-nonfree/-/commits/benh/debplate > > My intention is that debplate will (1) re-use existing well-known > software and formats as far as possible, and (2) be generally useful > for source packages that build multiple similar binary packages. > > If it succeeds, and if we adopt it for the linux and firmware source > packages, that should result in those packages being less unusual and > so easier for outsiders to contribute to. Also, if debplate gets > contributors from outside the kernel team, it would reduce our > maintenance burden. > > Have a look at it and see what you think. > > Ben. > -- Ben Hutchings You can't have everything. Where would you put it?
Attachment:
signature.asc
Description: This is a digitally signed message part