From: "Sławomir Lach" <slawek@lach.art.pl>
To: guix-devel@gnu.org
Subject: The way to promote GUIX package manager
Date: Wed, 26 Jan 2022 12:09:19 +0100 [thread overview]
Message-ID: <3101606.jC9oV0cg2h@localhost.localdomain> (raw)
Maybe it's road to security hell, but it is also very important for beginners
and developers.
Promote GNU GUIX by add support for installers/some scripts, which detects OS
and install software by package manager based on detection.
It is very hard to keep this kind of scripts fresh, because distribution will
evolve. One think, that developers should still do is keep instructions to
install guix package manager for some distros, but it is easier than keep
instruction to install ton of packages. Maybe creating script to install guix
for distributions and place it on single place + allow distro vendor to change
it? Solution is simple:
1. Keep older packages in GUIX repo, so developers could request older version
in scripts
2. Send patches to developers of these scripts, which will detects if there is
gnu guix package manager on target system installed and request to install
packages in exact versions, if there was gnu guix installed
USE CASES:
1. KDevelop could request to install developers tools, such like gcc, gdb,
php, etc.
2. Gaming managers could base on gnu guix instead of custom repository
3. ETC.
RESULT:
Simpler script to maintain, more distribution addressed, user do not have to
worry if script will work for one's distro, faster advantage in linux
ecosystem. Minus: possible security hell.
next reply other threads:[~2022-01-26 16:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 11:09 Sławomir Lach [this message]
2022-01-26 21:38 ` The way to promote GUIX package manager Ricardo Wurmus
2022-01-26 22:40 ` Yasuaki Kudo
2022-01-26 22:42 ` Ricardo Wurmus
2022-01-26 23:15 ` Yasuaki Kudo
2022-01-27 23:35 ` Bengt Richter
2022-01-27 23:55 ` Yasuaki Kudo
2022-01-28 1:43 ` David Pirotte
2022-01-28 14:48 ` Bengt Richter
2022-01-26 23:38 ` Vagrant Cascadian
2022-02-05 13:54 ` Ludovic Courtès
2022-02-05 20:39 ` Ricardo Wurmus
2022-02-06 18:54 ` Vagrant Cascadian
2022-02-06 19:19 ` Ricardo Wurmus
2022-02-14 17:23 ` 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=3101606.jC9oV0cg2h@localhost.localdomain \
--to=slawek@lach.art.pl \
--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).