From: Miles Fidelman <mfidelman@meetinghouse.net>
To: help-guix@gnu.org
Subject: question re. installing software & init system
Date: Thu, 31 Dec 2015 12:26:29 -0500 [thread overview]
Message-ID: <56856545.8050104@meetinghouse.net> (raw)
Hi Folks,
One thing that is very murky in the documentation is how to install
software that isn't packaged. I can't seem to find any clear
documentation on the process.
Several specific questions:
The recent PPT presentation on GUIX (to Inria) implies that packaging
can be as simple as writing a config file that tells GUIX to do a
"config; make; make install" on a source file built with the GNU tools
- do I NEED to package something or can I simply do a basic download,
untar, config, make, make install on a running system?
- does dmd handle standard sysvinit files (as are still most commonly
included in source packages)?
- and the there's the whole set of issues, recently raised, related to
language systems that maintain their own repos and build systems (e.g.,
CPAN) -- somehow, partial import of dependencies into the GUIX
environment does not seem usable
And a general comment on the documentation: Given that this is a
(sort-of) new distro, that does things VERY differently from previous
distros - it sure would be helpful to have the install documentation
provide both a very clear overview of the conceptual
approach/architecture (vs. items spread around various ppts), AND very
clear step-by-step instructions for:
- basic install & configuration
- installing & configuring packages (both those that run as services and
those that don't; including later re-configuration)
- installing & configuring software that isn't packaged
- with particular attention to how the installer, package system, and
init system work together
- and with attention to how these all work with other build systems
You know - something like the Debian install instructions or the FreeBSD
handbook.
Granted that documentation generally follows code; when doing things
radically differently, there's a lot to be said for writing
documentation FIRST - doing so provides a really good check on
conceptual clarity and usability. (It kind of makes it hard to do any
kind of testing, evaluating, or contributing without a good starting point.)
Thanks,
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
next reply other threads:[~2015-12-31 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 17:26 Miles Fidelman [this message]
2015-12-31 22:41 ` question re. installing software & init system Thompson, David
2016-01-01 17:52 ` Miles Fidelman
2016-01-01 18:23 ` Thompson, David
2016-01-01 19:09 ` swedebugia
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=56856545.8050104@meetinghouse.net \
--to=mfidelman@meetinghouse.net \
--cc=help-guix@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.
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).