I’ve just merged core-updates in ‘master’, yay!
As a reminder, some of the cool things for packagers:
• ‘search-path-specification’ can now specify files (instead of plain
directories) or even file pattern (for example, ‘catalog.xml’ for
libxml2, or maybe ‘\\.cmake$’ for CMake) This sh
* gnu/packages/video.scm (ffmpeg)[arguments][add-lib-to-run-path]:
Add $out/lib to the RUNPATH of libraries.
---
gnu/packages/video.scm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/video.scm b/gnu/packages/video.scm
index 2febd12..1b15577 100644
--- a/gnu
On Thu, Jan 15, 2015 at 10:42 PM, Ludovic Courtès wrote:
> Federico Beffa skribis:
>
>> A different look at aesthetics: Back in the mid '90, when Linux was
>> still an underground curiosity, many UNIX admins were starting to
>> install GNU user-land applications. To avoid name clashes with the
>>
Commit e48977e fixes a regression that was introduced with commit
7c594a2 a couple of days ago. Basically the fsck.ext[234] programs
embedded in the initrd would be broken, leading to an exception from the
initrd and to a REPL (which could just be left with “,q” to continue
booting.)
In related n
Federico Beffa skribis:
> On Wed, Jan 14, 2015 at 9:51 PM, Ludovic Courtès wrote:
>> Given that core-updates will soon be fully built (hopefully within 24h)
>> and ready to be merged, I would prefer to wait until that is done, and
>> then rebase wip-gobject-introspection on it and get it built.
宋文武 skribis:
> * gnu/packages/video.scm (ffmpeg)[arguments][add-lib-to-run-path]:
> Add $out/lib to the RUNPATH of libraries.
[...]
> -;; Add LIB to the RUNPATH of all the executables.
> +;; Add LIB to the RUNPATH of all the executables and libraries.
> (w
Ian Denhardt skribis:
> Latest word on the Symbola font from the FSF:
Thanks Ian for the update.
I forgot the details, but IIRC Alex Kost was the initial submitter.
What can be done here?
Ludo’.
On Thu, Jan 15, 2015 at 10:42:42PM +0100, Ludovic Courtès wrote:
> If there’s consensus to install the symlink, that’s fine with me (if we
> take that route, I would also suggest submitting a patch upstream so GCC
> installs the symlink.)
I am not in favour of adding such a symlink on our own and
