Re: Divvying up service definitions

Hi Efraim, On 2023-11-09 07:15, Efraim Flashner wrote: > I assume the define-maybe's aren't public, so I'd guess that shouldn't > cause a problem as long as they aren't exported. They're not public but they override definitions within the same file if more than one (define-maybe foo) is present (

Re: Divvying up service definitions

Hi Felix, On 2023-10-24 18:54, Felix Lechner wrote: > The number of services we offer strikes me as sufficiently small for > your "unsorted" scheme to remain easy to navigate. I can see your point here if we're to do estimates and interpolation based on the growth of the services so far although

Expressing system test dependencies

Hi, There are system tests that would benefit from being able to express that their results are dependent on the result of other tests, when these constitute independent units, especially when there are configuration variants present. (e.g. gnu/tests/gdm.scm) Consider the following files/system-t

Divvying up service definitions

Hi, As the gnu/services and gnu/home/services grow, I think we should consider divvying the services into stand-alone modules or subdirectories. Consider the ⌜dovecot-service-type⌝ in gnu/services/mail.scm: as of commit 'd22d2a05c389207f8cdcf824be7738b1499a987c' this service definition is nearly

Re: Shouldn't docbook-xml/xsl set XML_CATALOG_FILES?

Hi Hartmut, On 2017-03-26 12:28, Hartmut Goebel wrote: > Hi, > > within a few day I stumbled twice over this: When using docbook-xml or > docbook-xsl in a package description, one needs to set XML_CATALOG_FILES > to make xslproc (and others) find the catalogs. > > Shouldn't XML_CATALOG_FILES be

Plan for NFS (was: Herding file-systems)

Hi all, I've been thinking on a plan to address this old NFS question. The plan: 1. Allow the file-system `dependencies' field to accept arbitrary shepherd symbols as well. This can be done by having the `dependency->shepherd-service-name' in (gnu services base) also accept matching against a

Re: Building from git

Hi, On 2023-09-07 13:06, Simon Tournier wrote: > Hi, > > On Sat, 02 Sep 2023 at 11:03, Nicolas Débonnaire > wrote: > >> guix shell -D guix --pure >> ./bootstrap >> ./configure --localstatedir=/var --syscondir=/etc >> make > > [...] > >> Error: fontconfig:Didn't find expected font family. Per

Re: bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that

On 2023-08-27 02:13, 宋文武 wrote: > Maybe we can automatically report the failures as bugs, say every 7 > days, and remove a package if it still fail to build in 90 days? I'm not so sure about removing packages, personally if I'm in need of a package that happens to be broken I find it easier to fix

Re: Reusing code for a build-phase?

Hi Hartmut, On 2023-08-05 09:25, Hartmut Goebel wrote: > Hi, > > I'm currently packaging vagrant and some plugins. For all plugins an > additional phase is required, generating a json file, see below. Since this > is quite some code, I'd like to put it into some definition or some wrapper. > S

Examples of transient shepherd services?

Hi, Are there any examples that demonstrate how a custom non make-inetd-constructor transient shepherd service can be made and destroyed? Regards, Bruno

Re: [RFC] Cosmetic changes to define-configuration usage

On 2023-03-31 15:46, Maxim Cournoyer wrote:> I have some apprehension that if we start adding white space between the > fields here, we'll soon have people adding white space to many other > places (for consistency or other reasons), which I wouldn't welcome (I > value compactness, and since in Sc

Re: Automatically mapping services from System to Home

Hi Ludo’, On 2023-03-28 17:18, Ludovic Courtès wrote: > One idea I toyed with is automatic translation of service types from > System to Home. The service itself would look like this: > > --8<---cut here---start->8--- > (define-module (gnu home services syncth

[RFC] Cosmetic changes to define-configuration usage

Forwarded from: & [1] --8<---cut here---start->8--- apteryx: IMO the spacing between the fields should have been kept it makes things easier to read it's a nightmare if the records grow very large mirai: I w

Brainstorming ideas for define-configuration

Co-authored-by: Felix Lechner After spending some time with old and new Guix services, I'd like to suggest some potential improvements to our define-configuration macro: User-specified sanitizer support === The sanitiz

Herding file-systems

Co-authored-by: Felix Lechner Some observations and potential plans of action to improve file-system handling and proper NFS support within Guix. Relaxing dependency field of file-system record type === Guix currently

Relocating some procedures into (guix utils)

IMO there are some procedures (or even modules) that could be relocated into (guix utils) as their utility is more general than what their module names would suggest. Good candidates to relocate into (guix utils): * (gnu home services utils) * list-of, interpose, alist?, list-of-string? from (gn

Re: Improving how NGINX modules are used and built

On 2023-01-09 10:51, Ludovic Courtès wrote: > Hello! > > mirai skribis: > >> An oddity of how nginx modules are packaged in guix is that they all place >> the .so file under /etc/nginx/modules which is an odd directory to place >> library object files. > > To me that should be treated as a bug