Hello, On Mon 01 Apr 2024 at 02:50pm +02, Holger Wansing wrote:
> I now tend to switch to another approach (also proposed similarly by Adam): > > instead of relying on the rtd-theme package in the default install path of the > package installed by DSA, I will use the infrastructure in 1ftpfiles and > 7doc of webmaster's cron repo, to (always) fetch the latest version of that > package (and two more packages, which the former depends on: > fonts-font-awesome > and fonts-lato, to get the needed fonts) and unpack+copy them into > a dedicated path inside the www build tree. > > That path will be synced to the static www mirrors, and we can symlink > to it from the manuals. > (And the content of that path will automatically be kept up-to-date on > the unstable version of packages, so we don't get outdated/orphaned > copies of that packages in the isolated path.) > I want the unstable version of that packages here, since they need to > incorporate with the unstable version of the different manuals (like > debian-policy), and those packages are built by buildd, so unstable. > > How does that sound in the light of Debian guidelines and best practice? > > Is it ok, to have such "isolated copies" of packages as described above? > > I have not much experience in similar things, so I would like to get > some comments here, please. I mean, it seems okay to me, but it's up to the web team really. -- Sean Whitton
signature.asc
Description: PGP signature