Jonas Smedegaard <dr@jones.dk> writes: >> Now coming fonts-roboto, we need to package it from the actual >> upstream. > > Are you informing that you'll do the work, or who are "we" in above? We as in pkg-fonts team, it can be myself but I won't promise :-). > > Remember to also check build-rdeps! Thanks will do. > > Makes good sense to track Roboto in new source package fonts-roboto. Yes will do that. > > Droid, however seems not moved to Noto but instead abandoned upstream. > I suggest to keep current source package for Droid, move it to section > oldlibs, file bugreports to rdepends warning it might be dropped and > encouraging to consider use Noto instead. Now there are some questions: 1. How long do we keep fonts-droid? For stretch release? 2. By default fonts-droid ships Fallback fonts also but upstream has updated it in newer release. So drop Fallback from fonts-droid and create new package tracking upstream Vcs and add dependencies to fonts-droid? > > We can then either > a) keep Droid as-is for eternity, > b) gradually bump severy of those bugreports as we get closer to > freeze and drop package before freeze, or >c) update source package (eventually renaming it just > to look nicer) if we learn that upstream maintenance is renewed (either > by Google who commissioned the fonts, or Ascender who seems to own > copyright for it, or Christian Robertson who authored it originally, or > whoever else choosing to step up). Not clear what you mean by point "c" can you please elaborate?.
Attachment:
signature.asc
Description: PGP signature