unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thorsten Wilms <t_w_@freenet.de>
To: guix-devel@gnu.org
Subject: Re: Review of pros and cons of package managers including Guix
Date: Thu, 8 Nov 2018 10:43:23 +0100	[thread overview]
Message-ID: <2de6a0a3-3d2b-caf5-4c72-37e9eafdb28f@freenet.de> (raw)
In-Reply-To: <b3e386dd-3629-d868-3133-82b325c5a783@riseup.net>

On 08/11/2018 10.09, swedebugia wrote:
> 
> https://www.slant.co/topics/344/~best-linux-package-managers
> 
> Insights from the Guix-section:
> 
> 4 pros: (missing the roll-back feature) see link.
> 
> 1 cons:
> 
> "Cannot handle filetypes that have different semantics across different 
> versions
> While the functional approach that Guix takes is great for sandboxing 
> binary artifacts of packages, it seriously lacks any power in handling 
> configuration files or user data. It's difficult to upgrade and 
> downgrade files where semantics and syntax can change between versions."
> 
> Do you agree with this critique?

The whole page is far from a worthwhile comparison, because the "cons" 
and "pros" are all over the place. Characteristics that are listed  as 
either for one manager do not appear for all others that have them, too.

This specific con could be listed for most, if not all others, too, 
right? Curious, if anyone knows an exception.

The best handling of configuration files I got to know is offered by 
Debian, which, if a package comes with a new configuration file, asks 
what to do about it. Better than nothing, but still not exactly a good 
user experience. There quite simply isn't the right level of granularity 
and encoding of intentions given with plain text configuration files.


-- 
Thorsten Wilms

thorwil's design for free software:
http://thorwil.wordpress.com/

  reply	other threads:[~2018-11-08  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08  9:09 Review of pros and cons of package managers including Guix swedebugia
2018-11-08  9:43 ` Thorsten Wilms [this message]
2018-11-08 15:31   ` Adam Van Ymeren
2018-11-08 16:11     ` swedebugia
2018-11-11 13:33 ` Ludovic Courtès

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=2de6a0a3-3d2b-caf5-4c72-37e9eafdb28f@freenet.de \
    --to=t_w_@freenet.de \
    --cc=guix-devel@gnu.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).