unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Runciter via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: guix-devel@gnu.org
Subject: Re: Unofficial channel 'whispers' with services and packages
Date: Mon, 18 Nov 2024 02:51:19 +0800	[thread overview]
Message-ID: <87serpbsns.fsf@whispers-vpn.org> (raw)
In-Reply-To: 87fro64q84.fsf@gnu.org

Ludovic Courtès <ludo@gnu.org> writes:

Hello Guix,

> Hello Runciter,
>
> Lots of interesting things in there!
>
> If I could have a wish list of things to integrate in Guix proper, it
> would be this:
>
>> * dictd: the original programs for the DICT protocol. Includes the dict
>>   client and dictd server, which dico and dicod know how to
>>   emulate. Also includes the dictfmt utility, which is useful to express
>>   DICT dictionaries from human-written sources or other dictionary
>>   formats, for which GNU dico has no equivalent to my knowledge. I'm
>>   just the packager not an author.
>>
>> * freedict-tools: I packaged helper tools to compile the freedict
>>   multilingual dictionaries. I'm just the packager not an author.
>>
>> * freedict-dictionaries: package containing a subset of the
>>   freedict-dictionaries, intended for a local installation on a Guix
>>   system. I think the subset which I packaged corresponds exactly to the
>>   Freedict bilingual dictionaries which are human-written. The Freedict
>>   project also has a system which copulates 2 bilingual dictionaries
>>   sharing a common language into a third new automatically generated
>>   bilingual dictionary, I don't think my package outputs any of the many
>>   dictionaries which are expressed by this system. I'm just the packager
>>   not an author.

I've just sent a cover letter to the patches mailing list, I'm waiting
for it to show up before sending 4 patches.

There's 4 packages and not 3 finally because 'libmaa' is a dependency of
dictd.

Everything compiles and cross-compiles, however the
'freedict-dictionaries' build is non-deterministic. One reason,
hopefully the only reason for the non-deterministic output is that the
'dictzip' program includes a timestamp header in the compressed files it
produces. The man page of dictzip does not document a way to modify or
get rid of the timestamp header.

There is a possible fix I have not tried yet, which looks like it's
going to work: I could probably output non-compressed binary dictionary
files (*.dict) instead of dictzipped dictionary files (*.dict.dz). In
order to do it, an 'install-base' target needs to be modified. This
target is found in mk/dicts.mk inside the toolchain package
'freedict-tools'. I have not found how this could be easily configured
at build-time, at the moment I would only know how to do it with a patch
to the 'freedict-tools' package.

What's your policy, or what's your call for this case? Do you want me to
try my fix, or do you find it preferable to sacrifice determinism in
exchange for enjoying dictzip compression of the output, which also
amounts to staying faithful to the upstream intended installation
contents? Other suggestions?

Runciter



      parent reply	other threads:[~2024-11-17 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 14:36 Unofficial channel 'whispers' with services and packages Runciter via Development of GNU Guix and the GNU System distribution.
2024-11-04 21:57 ` Ludovic Courtès
2024-11-06 16:51   ` Runciter via Development of GNU Guix and the GNU System distribution.
2024-11-17 18:51   ` Runciter via Development of GNU Guix and the GNU System distribution. [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87serpbsns.fsf@whispers-vpn.org \
    --to=guix-devel@gnu.org \
    --cc=runciter@whispers-vpn.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).