Quoting Todd Zullinger (2024-08-15 01:12:01)
> Piper McCorkle wrote:
> > On Wednesday, 14 August 2024 16:43:54 CDT Agathe Porte wrote:
> >> Or maybe I could tar the upstream .git folder and store everything else
> >> as plain files? But still a binary blob in source package. And
> >> extracting the
On Wed, Aug 14, 2024 at 11:43:54PM +0200, Agathe Porte wrote:
> Note that the qmk tool does require a git repository to work, so I did
> not consider shipping only the code.
Is there any reason qmk couldn't be patched to accept a plain directory
as an alternative to a git repository? It looks lik
Piper McCorkle wrote:
> On Wednesday, 14 August 2024 16:43:54 CDT Agathe Porte wrote:
>> Or maybe I could tar the upstream .git folder and store everything else
>> as plain files? But still a binary blob in source package. And
>> extracting the tar into a .git in the filesystem in /usr/share/ may
>
On Wednesday, 14 August 2024 16:43:54 CDT Agathe Porte wrote:
> Or maybe I could tar the upstream .git folder and store everything else
> as plain files? But still a binary blob in source package. And
> extracting the tar into a .git in the filesystem in /usr/share/ may
> raise a lot of Lintian war
Hello everyone,
I have recently packaged qmk¹ into debian² (see rationale³).
However the tool still needs to git clone the qmk_firmware repository⁴
at runtime before being able to do any work. This is what the
autopkgtest currently does⁵, with the needs-internet restiction⁶.
¹ https://github.com
5 matches
Mail list logo
