Hi Ahmad,
Le 2025-01-20 21:29, Ahmad Khalifa a écrit :
Does this make it 1 source package with 2 orig tarballs then, or should
I split it completely into 2 source packages?
Perhaps one source won't work on git unless I switch to a plain repo
based on tarballs.
It will probably be easier to manage that with a separate source
package, as their builds are completely independant anyway.
Yes, it's a compiled tool written in freebasic that can download the
wiki source to a cache dir, then use that cache dir to build
html/chm/txt/fbhelp formats. It can run on the cache only, but the tool
currently requires pcre3 (libpcre.so) so I only managed to make it work
locally outside sbuild with lots of manual hacks.
I think the idea above is much cleaner even if I have to track
different git repos and tarballs.
It's a bit borderline as it's generated from a source code that will not
be part of the source package, but on the other hand it avoids the
difficult issue of guessing which revision of each page is relevant to
which released version while downloading the sources. To make that
really clean, it would help if upstream could provide versioned archives
of the source and generator code. Anyway in the meantime the source
requirement of the DFSG specifically mentions "the program", html
documentation (excluding embedded scripts) is not a program, it can
still be manually edited, and could probably be converted back to its
wiki source form if a tool is written for that, so I believe that it's
fine to proceed that way.
Cheers,
--
Julien Plissonneau Duquène
