I wrote:
> Here are the inode numbers as reported by ls -lia:
>
> mhw:/tmp$ ls -lia nix-build-make-boot0-3.82.drv-0/
> total 16
> 7274550 drwxr-xr-x 3 guix-builder1 guix-builder 4096 Oct 8 17:19 .
> 7072375 drwxrwxrwt 9 root root 4096 Oct 8 17:19 ..
> 7272956 -rw-r--r-- 1 guix-bu
Should the transltion be done in Womb?
I don't think that would be practical.
These descriptions (in HTML form) will end up on www.gnu.org. Therefore
the web translators (not the TP translators) will be translating them.
I believe po format is involved and thus could conceivably be used
wi
l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>
>> Nikita Karetnikov writes:
>>
>>> OK, I fetched the tarballs. Now I’m getting this error.
>>>
>>>
>>> $ ./pre-inst-env guix build -K hello
>>>
>>> [...]
>>>
>>> make-3.82/main.c
>>> make-3.82/README.OS2
>>> make-3.82/remote-cst
l...@gnu.org (Ludovic Courtès) skribis:
> To address that, I think we should move patch handling from the build
> system to the ‘origin’ objects. That is, we would write:
>
> (package
> ...
> (source (origin
> (uri ...)
> (sha256 ...) ; hash of the upstr
Hi Ludovic et al,
>> Perhaps it would be best to keep all canonical package descriptions,
>> short and long, in a single file under revision control somewhere, such
>> as in womb. They would then be available for anyone who needs them,
>> should any need arise in the future and it would be easier
Hi Ludovic et al,
>> Perhaps it would be best to keep all canonical package descriptions,
>> short and long, in a single file under revision control somewhere, such
>> as in womb. They would then be available for anyone who needs them,
>> should any need arise in the future and it would be easier
Andreas Enge skribis:
> I just pushed a patch for Qt 5.1.1.
Good, congratulations!
> It builds on my machine, but as there is no application using it so
> far, it may or may not work. Also, the build uses
> sse/sse2/... instructions according to what is available on the
> processor; we might wi
Hi,
I just pushed a patch for Qt 5.1.1. It builds on my machine, but as there
is no application using it so far, it may or may not work. Also, the build
uses sse/sse2/... instructions according to what is available on the processor;
we might wish to disable all or at least the most advanced of the
