Hi!
Thank you very much for your feedback.
I have just pushed the first part of the second video. May someone
test it and give feedback too?
Regards :)
Laura
Leo Famulari writes:
> On Sat, Feb 23, 2019 at 09:03:10PM -0500, guix-comm...@gnu.org wrote:
>> iyzsong pushed a commit to branch master
>> in repository guix.
>>
>> commit 590b989c95f5b72dfe4b9928d1426fb7d35d1428
>> Author: Pkill -9
>> Date: Sat Feb 23 10:12:32 2019 +
>>
>> gnu: fon
Hey,
In short, following on from some previous emails about Patchwork [1] and
tracking and inspecting how Guix changes over time [2], I've got to the
point where I have a very rough setup for building packages changed by
patches sent to the guix-patches mailing list.
1: http://lists.gnu.org/archi
Thanks for clarifying this.
Then I 100% agree with your approach.
I should have a little bit more free time in the coming days, so I'll (finally)
get down to write the tlpdb importer :)
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Pierre Neidhardt writes:
> Would that still be needed if we implement a tlpdb-based importer?
The importer only helps you generate the initial package definition.
A tlpdb-based importer cannot do magic. The tlpdb file tells it what
files are expected to be provided by the package and what fi
Hi,
Would that still be needed if we implement a tlpdb-based importer?
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Hi Laura and sirgazil,
I was able to build videos in 01-installation-from-script following the
updated informations in the README, that is:
1. environment.sh
2. install-fonts.sh
3. cd 01-installation-from-script/ && buildall.sh
the only "strange" message I see during the build is
--8<--
Hey Guix,
Tex Live packages often have a complicated source file layout. They
don’t usually come in a nice self-contained tarball. Instead they are a
mosaic of files that are sourced from different parts of the Tex Live
SVN tree. For many Tex Live packages the “source” field is
insufficient, so
On Fri, 01 Mar 2019 12:01:45 +0100
Giovanni Biscuolo wrote:
> my personal workflow in this case is to use the [env] to build and
> "outside env" for editing and analisys (e.g. with rmlint), BTW I agree
> with you ls and less are *very* useful inside the container
Gábor presented today another so
El 28/02/19 a las 4:52 p. m., Laura Lazzati escribió:
Hi!
Thanks for the steps!
+ Text is not rendered with the appropriate font (known issue).
+ Firefox 65.0.1 says "Video can't be played because the file is corrupt."
We are currently testing everything with vlc and mpv, but thanks for this t
Ricardo Wurmus writes:
[...]
> There will be lots of files. That’s expected. They are frames for the
> command line videos. Eventually all of them would be converted from txt
> to png.
OK I got it
I've updated my repo with current master and restarted building, I'll
report back ASAP
Thanks
Hi Björn,
Björn Höfling writes:
[...]
> since the environment is a CONTAINER, it contains really nothing
> besides what you explicitly add to it.
I was aware of this :-)
> I added those variables. It is
> really helpful to have at least "ls" and "less", and during development
> some more tool
12 matches
Mail list logo