Protecting prerequisites from GC
Hello, On popular demand ;-), commit 6e37066 finally exposes the daemon’s --gc-keep-derivations and --gc-keep-outputs options, which control exactly what the daemon will reclaim (see documentation below.) The commit is small, because that functionality was already present in the Nix daemon, just not exposed in guix-daemon. The idea is that on a developer’s machine the daemon would run with --gc-keep-outputs (and --gc-keep-derivations, which is the default.) I think this addresses a longstanding inconvenience, where running the GC would delete all the build tools and sources, unless they happened to be live. Comments welcome. Ludo’. ‘--gc-keep-outputs[=yes|no]’ Tell whether the garbage collector (GC) must keep outputs of live derivations. When set to “yes”, the GC will keep the outputs of any live derivation available in the store—the ‘.drv’ files. The default is “no”, meaning that derivation outputs are kept only if they are GC roots. ‘--gc-keep-derivations[=yes|no]’ Tell whether the garbage collector (GC) must keep derivations corresponding to live outputs. When set to “yes”, as is the case by default, the GC keeps derivations—i.e., ‘.drv’ files—as long as at least one of their outputs is live. This allows users to keep track of the origins of items in their store. Setting it to “no” saves a bit of disk space. Note that when both ‘--gc-keep-derivations’ and ‘--gc-keep-outputs’ are used, the effect is to keep all the build prerequisites (the sources, compiler, libraries, and other build-time tools) of live objects in the store, regardless of whether these prerequisites are live. This is convenient for developers since it saves rebuilds or downloads.
Google Summer of Code: GNUnet and Guix
On 02/06/2014 01:25 PM, Christian Grothoff wrote: > Well, aside from that our plan was to package for GNU Guix and > then use Guix to deploy to legacy distributions, I am unconvinced > that "merely" packaging is an appropriate activity for a summer > of *Code*. At least I had the impression that the goal was to write > a bit more substantial code than what is typically required to script > a package. Make a GNUnet package for GNU Guix is already done. I recently submitted patches for that. > > Still, it's of course great to hear that we'd have somebody willing > and able to mentor this, so we should keep this in mind if/when student > applications are submitted. What I want to see in the near future is for GNU Guix to propagate updates using GNUnet. I am willing to contribute to both projects in this direction and hopefully can mentor someone or be mentored by someone. Regards, Sree Harsha
Re: [PATCH] gnu: glade New variable
On Thu, Feb 06, 2014 at 07:03:13PM +0100, Ludovic Court??s wrote: > --- a/gnu/packages/gnome.scm > +++ b/gnu/packages/gnome.scm > @@ -530,3 +530,31 @@ API add-ons to make GTK+ widgets OpenGL-capable.") > (description > "ekiga is a gobject-based plugins engine, and is targetted at giving nthe API") > (license lgpl2.0+))) The patch didn???t apply because of the above (great initiative! ;-)), so I manually applied it. Sorry. I should keep the experimental stuff separate. -- PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key. signature.asc Description: Digital signature
Re: [PATCH] gnu: glade New variable
John Darrington skribis: > * gnu/packages/gnome.scm (glade): New variable. Applied, thanks! > --- a/gnu/packages/gnome.scm > +++ b/gnu/packages/gnome.scm > @@ -530,3 +530,31 @@ API add-ons to make GTK+ widgets OpenGL-capable.") > (description > "ekiga is a gobject-based plugins engine, and is targetted at giving > nthe API") > (license lgpl2.0+))) The patch didn’t apply because of the above (great initiative! ;-)), so I manually applied it. > +(synopsis "GTK+ RAD tool") > +(description "Glade is a RAD tool to enable quick & easy development of > +user interfaces for the GTK+ toolkit and the GNOME desktop environment.") I expanded “RAD” here. Ludo’.
Re: luajit recipe
Raimon Grau skribis: > From 922d9b5e0e4d8332e3f742d1e7954feb93dbdabe Mon Sep 17 00:00:00 2001 > From: Raimon Grau > Date: Thu, 6 Feb 2014 01:43:31 +0100 > Subject: [PATCH] gnu: Add luajit Applied, thanks! Note that I added a GNU ChangeLog-style commit entry–see ‘HACKING’ for details. Ludo’.
Changes made to pysqlite-2.6.3 without changing the version number
Hello all,
We don't have a working pysqlite-2.6.3 package in Guix right now. The
reason is that the upstream source tarball has changed without changing
the version number. For the record, I've attached the diff here.
I mailed the author about this, but he never replied. It would be good
if someone other than me would email him too, to ask him to change the
version number.
Mark
diff -ruN pysqlite-2.6.3-OLDER/doc/default.css pysqlite-2.6.3/doc/default.css
--- pysqlite-2.6.3-OLDER/doc/default.css 1969-12-31 19:00:00.0 -0500
+++ pysqlite-2.6.3/doc/default.css 2013-10-18 04:32:34.0 -0400
@@ -0,0 +1,10 @@
+@import url(docutils.css);
+@import url(silvercity.css);
+
+div.code-block{
+margin-left: 2em ;
+margin-right: 2em ;
+background-color: #ee;
+font-family: "Courier New", Courier, monospace;
+font-size: 10pt;
+}
diff -ruN pysqlite-2.6.3-OLDER/doc/docutils.css pysqlite-2.6.3/doc/docutils.css
--- pysqlite-2.6.3-OLDER/doc/docutils.css 1969-12-31 19:00:00.0 -0500
+++ pysqlite-2.6.3/doc/docutils.css 2013-10-18 04:32:34.0 -0400
@@ -0,0 +1,260 @@
+/*
+:Author: David Goodger
+:Contact: good...@users.sourceforge.net
+:Date: $Date: 2005-04-25 22:24:49 +0200 (Mon, 25 Apr 2005) $
+:Version: $Revision: 3256 $
+:Copyright: This stylesheet has been placed in the public domain.
+
+Default cascading style sheet for the HTML output of Docutils.
+*/
+
+/* "! important" is used here to override other ``margin-top`` and
+ ``margin-bottom`` styles that are later in the stylesheet or
+ more specific. See http://www.w3.org/TR/CSS1#the-cascade */
+.first {
+ margin-top: 0 ! important }
+
+.last {
+ margin-bottom: 0 ! important }
+
+.hidden {
+ display: none }
+
+a.toc-backref {
+ text-decoration: none ;
+ color: black }
+
+blockquote.epigraph {
+ margin: 2em 5em ; }
+
+dl.docutils dd {
+ margin-bottom: 0.5em }
+
+/* Uncomment (and remove this text!) to get bold-faced definition list terms
+dl.docutils dt {
+ font-weight: bold }
+*/
+
+div.abstract {
+ margin: 2em 5em }
+
+div.abstract p.topic-title {
+ font-weight: bold ;
+ text-align: center }
+
+div.admonition, div.attention, div.caution, div.danger, div.error,
+div.hint, div.important, div.note, div.tip, div.warning {
+ margin: 2em ;
+ border: medium outset ;
+ padding: 1em }
+
+div.admonition p.admonition-title, div.hint p.admonition-title,
+div.important p.admonition-title, div.note p.admonition-title,
+div.tip p.admonition-title {
+ font-weight: bold ;
+ font-family: sans-serif }
+
+div.attention p.admonition-title, div.caution p.admonition-title,
+div.danger p.admonition-title, div.error p.admonition-title,
+div.warning p.admonition-title {
+ color: red ;
+ font-weight: bold ;
+ font-family: sans-serif }
+
+/* Uncomment (and remove this text!) to get reduced vertical space in
+ compound paragraphs.
+div.compound .compound-first, div.compound .compound-middle {
+ margin-bottom: 0.5em }
+
+div.compound .compound-last, div.compound .compound-middle {
+ margin-top: 0.5em }
+*/
+
+div.dedication {
+ margin: 2em 5em ;
+ text-align: center ;
+ font-style: italic }
+
+div.dedication p.topic-title {
+ font-weight: bold ;
+ font-style: normal }
+
+div.figure {
+ margin-left: 2em }
+
+div.footer, div.header {
+ font-size: smaller }
+
+div.line-block {
+ display: block ;
+ margin-top: 1em ;
+ margin-bottom: 1em }
+
+div.line-block div.line-block {
+ margin-top: 0 ;
+ margin-bottom: 0 ;
+ margin-left: 1.5em }
+
+div.sidebar {
+ margin-left: 1em ;
+ border: medium outset ;
+ padding: 1em ;
+ background-color: #ee ;
+ width: 40% ;
+ float: right ;
+ clear: right }
+
+div.sidebar p.rubric {
+ font-family: sans-serif ;
+ font-size: medium }
+
+div.system-messages {
+ margin: 5em }
+
+div.system-messages h1 {
+ color: red }
+
+div.system-message {
+ border: medium outset ;
+ padding: 1em }
+
+div.system-message p.system-message-title {
+ color: red ;
+ font-weight: bold }
+
+div.topic {
+ margin: 2em }
+
+h1.title {
+ text-align: center }
+
+h2.subtitle {
+ text-align: center }
+
+hr.docutils {
+ width: 75% }
+
+ol.simple, ul.simple {
+ margin-bottom: 1em }
+
+ol.arabic {
+ list-style: decimal }
+
+ol.loweralpha {
+ list-style: lower-alpha }
+
+ol.upperalpha {
+ list-style: upper-alpha }
+
+ol.lowerroman {
+ list-style: lower-roman }
+
+ol.upperroman {
+ list-style: upper-roman }
+
+p.attribution {
+ text-align: right ;
+ margin-left: 50% }
+
+p.caption {
+ font-style: italic }
+
+p.credits {
+ font-style: italic ;
+ font-size: smaller }
+
+p.label {
+ white-space: nowrap }
+
+p.rubric {
+ font-weight: bold ;
+ font-size: larger ;
+ color: maroon ;
+ text-align: center }
+
+p.sidebar-title {
+ font-family: sans-serif ;
+ font-weight: bold ;
+ font-size: larger }
+
+p.sidebar-subtitle {
+ font-family: sans-serif ;
+ font-weight: bold }
+
+p.topic-title {
+ font-weight: bold }
+
+pre.address {
+ margin-bottom: 0 ;
+ margin-top: 0 ;
+ font-family: serif ;
+ fon
Re: Fwd: [GNUnet-developers] Google Summer of Code: GNUnet and Guix
Hi! (Adding gnunet-developers.) Sree Harsha Totakura skribis: > Anyone interested in mentoring for GSoC 2014? [...] > What I want to see in the near future is for GNU Guix to propagate > updates using GNUnet. I am willing to contribute to both projects in > this direction and hopefully can mentor someone or be mentored by someone. I’d be happy to see someone work on this project, and to mentor them! This is something we discussed last year [0], although it didn’t go anywhere at the time. I think we should also propose other Guix-related projects. Volunteers? Thanks, Ludo’. [0] http://lists.gnu.org/archive/html/bug-guix/2013-03/msg00085.html
Re: university group willing to contribute to GUIX
Felipe López skribis: > 2014-02-03 Quiliro Ordóñez Baca : > >> >> Depending on what you really want to do, it might be that students would >> be better off contributing to a well-established distro like Trisquel. >> >> >> The university must present a result. What result will the students >> present? I must propose that so that they get interest in contributing. >> > > Steap suggested on IRC to start developing a GUI for the package manager, > isn't that a good project? That’s a good idea. Technically, it might be even better to write PackageKit bindings, which would then allow us to use existing PackageKit GUIs. The other obvious task for anyone joining is writing more package definitions, of course. Thanks, Ludo’.
Fwd: [GNUnet-developers] Google Summer of Code: GNUnet and Guix
Anyone interested in mentoring for GSoC 2014? Original Message Subject: [GNUnet-developers] Google Summer of Code: GNUnet and Guix Date: Thu, 06 Feb 2014 15:27:31 +0100 From: Sree Harsha Totakura To: gnunet-develop...@gnu.org, guix-devel@gnu.org On 02/06/2014 01:25 PM, Christian Grothoff wrote: > Well, aside from that our plan was to package for GNU Guix and > then use Guix to deploy to legacy distributions, I am unconvinced > that "merely" packaging is an appropriate activity for a summer > of *Code*. At least I had the impression that the goal was to write > a bit more substantial code than what is typically required to script > a package. Make a GNUnet package for GNU Guix is already done. I recently submitted patches for that. > > Still, it's of course great to hear that we'd have somebody willing > and able to mentor this, so we should keep this in mind if/when student > applications are submitted. What I want to see in the near future is for GNU Guix to propagate updates using GNUnet. I am willing to contribute to both projects in this direction and hopefully can mentor someone or be mentored by someone. Regards, Sree Harsha ___ GNUnet-developers mailing list gnunet-develop...@gnu.org https://lists.gnu.org/mailman/listinfo/gnunet-developers
Re: university group willing to contribute to GUIX
2014-02-03 Quiliro Ordóñez Baca : > > Depending on what you really want to do, it might be that students would > be better off contributing to a well-established distro like Trisquel. > > > The university must present a result. What result will the students > present? I must propose that so that they get interest in contributing. > Steap suggested on IRC to start developing a GUI for the package manager, isn't that a good project? Students could use it to get familiar with Guix and free software development. That project would also give you autonomy; you will still need to communicate with Guix developers, but you will be able to use your own project management system, repository, conventions, etc. In eight months I would not expect a "version 1.0" software from inexperienced students, though. I think the results should be guessed by you and the mentors from the university based on your experience and the experience of the students in free software development and tools. -- Luis Felipe López Acevedo http://sirgazil.bitbucket.org/
Re: [PATCH] gnu: gnu-pw-mgr: Upgrade to 1.1
On Wed, Feb 05, 2014 at 03:48:19PM -0600, Eric Bavier wrote: > * gnu/packages/gnu-pw-mgr.scm (gnu-pw-mgr): Upgrade to 1.1 Applied, thanks! Andreas
