Re: Goals for 0.4
Probably, one will still need to install fontconfig. Maybe you could try out if emacs works for you without fontconfig. It did, to my surprise, for me. I just upgraded my profile and remove gs-fonts, and Emacs still displays properly. So unless there’s an evil cache somewhere, I’d say that it works. I can confirm Emacs working fine on a clean install without installing any additional font packages, which I take to confirm your findings. Best wishes, Alex
Re: Goals for 0.4
Andreas Enge andr...@enge.fr skribis: On Wed, Sep 25, 2013 at 03:13:25PM +0200, Ludovic Courtès wrote: Yes, so normally installed GTK+ apps will work out of the box now. The only thing we could document is that fonts installed in the user profile will automatically be picked up. Probably, one will still need to install fontconfig. Maybe you could try out if emacs works for you without fontconfig. It did, to my surprise, for me. I just upgraded my profile and remove gs-fonts, and Emacs still displays properly. So unless there’s an evil cache somewhere, I’d say that it works. Ludo’.
Re: Goals for 0.4
On Wed, Sep 25, 2013 at 03:13:25PM +0200, Ludovic Courtès wrote: Yes, so normally installed GTK+ apps will work out of the box now. The only thing we could document is that fonts installed in the user profile will automatically be picked up. Probably, one will still need to install fontconfig. Maybe you could try out if emacs works for you without fontconfig. It did, to my surprise, for me. Andreas
Re: Goals for 0.4
On Thu, Aug 29, 2013 at 10:42:23PM +0200, Andreas Enge wrote: On Thu, Aug 29, 2013 at 02:34:27PM +0200, Ludovic Courtès wrote: • Manual: improve as we see fit; notably add a section on font usage for X applications. I would volunteer for this one. The main problem that gtk+ applications would not find a font unless the user installed gs-fonts should be solved by the latest commit. I added gs-fonts as an input to fontconfig and added it to its configuration file. Andreas
‘--no-substitutes’ is ignored on i686 (was: Goals for 0.4)
• Guix must be usable with the old Guile 2.0.5, since that’s what some distros provide. At the GHM I realized that some people had weird bugs with that Guile, notably in the substituter. I fixed a couple of bugs, but there may be others around. So, to 2.0.5 users: please run ‘make check’, use Guix and in particular the substituter, and report bugs! I’m using the latest version of Guile. And I’ve already mentioned this (though, it might be a new issue): ‘--no-substitutes’ doesn’t work on my system at all. It’s completely ignored. (I haven’t tested on a different machine.) I’ll try to look into it when I finish with generations and MIPS. pgpYkEJn0gHUH.pgp Description: PGP signature
MIPS64/N64 support (was: Goals for 0.4)
• MIPS64/N64 support: the bootstrap tarballs are now all available through cross-compilation from x86_64, so it’s “just” a matter of feeding them in bootstrap.scm and trying out. I’m also interested in this one. Oh, I forgot that I’ll need five tarballs, not two [1]. Can I get the other three somewhere? Otherwise, I’ll probably try to cross-compile them myself. [1] http://www.fdn.fr/~lcourtes/tmp/ pgpmTclcc3YOy.pgp Description: PGP signature
Re: Goals for 0.4
On 09/02/2013 09:38 PM, Ludovic Courtès wrote: That is, try to install something that’s available on hydra.gnu.org, and check that it downloads correctly, and prints “Please consider upgrading Guile to get proper progress report”. It does exactly that. Cyril.
Re: Goals for 0.4
jema...@gnu.org (Jose E. Marchesi) skribis: I just realized that we can do even better: have --list-generations output recutils-formatted data (using ‘object-fields’). Then, if we do it right, the output can just be piped to ‘recsel’ to select entries of a certain age, to display specific fields, etc. Like: generation-number: 1 date: 2013-05-07 However, I don’t know exactly how to represent both the generations and the list of packages in each generation in a single recutils stream. José, how can the relations between “generation” records and “package” records be expressed? You can have two record sets: one for generations, one for packages. A foreign key can relate them. Something like this: Perfect, thanks! Ludo’.
Goals for 0.4
Hello! So, what do we put in 0.4, and when do we release it? First, I’d like to release 0.4 by (or on) GNU’s 30th birthday, which is on Sep. 28th [0]. On the 28th, I’d also like to have a bootable QEMU image built with Guix, featuring at least the init system (dmd), a console login, and bare utilities. What I would really like to see in 0.4: • Guix must be usable with the old Guile 2.0.5, since that’s what some distros provide. At the GHM I realized that some people had weird bugs with that Guile, notably in the substituter. I fixed a couple of bugs, but there may be others around. So, to 2.0.5 users: please run ‘make check’, use Guix and in particular the substituter, and report bugs! • Packages: as already discussed, more packages, anything that makes the distro more useful (having Git is a must.) A package a day keeps the competition away. ;-) • Core updates: in particular libc 2.18. Possibly switch to GCC 4.8 as the default compiler. • APIs: new or extended APIs for building stand-alone images. I’ve been looking into that recently, notably with the initrd stuff. • New ‘--list-generations’ and ‘--delete-generations’ options for ‘guix package’. • Manual: improve as we see fit; notably add a section on font usage for X applications. Optional goals: • MIPS64/N64 support: the bootstrap tarballs are now all available through cross-compilation from x86_64, so it’s “just” a matter of feeding them in bootstrap.scm and trying out. • Rebuilt bootstrap binaries (aka. the “Fixed Point Project”, more on that later.) • Python 3, and related packaging changes. Anything else? What do people think? Ludo’. [0] https://www.gnu.org/gnu30/ pgpp4y_ewp4ro.pgp Description: PGP signature
Re: Goals for 0.4
Andreas Enge andr...@enge.fr skribis: On Thu, Aug 29, 2013 at 02:34:27PM +0200, Ludovic Courtès wrote: • Manual: improve as we see fit; notably add a section on font usage for X applications. I would volunteer for this one. • Python 3, and related packaging changes. And for some work on this one. Thanks! Ludo’.