From: "Germán Arias" <german@xelalug.org>
To: Brandon Invergo <brandon@invergo.net>
Cc: guile-user@gnu.org, bug-guix@gnu.org
Subject: Re: GNU Guix 0.2 released
Date: Thu, 16 May 2013 01:29:41 -0600 [thread overview]
Message-ID: <a909ec44336569e523a2da7a0578c87f@german-desktop> (raw)
In-Reply-To: <871u98d3pq.fsf@invergo.net>
On 2013-05-15 02:53:05 -0600 Brandon Invergo <brandon@invergo.net> wrote:
> Hi Germán,
>
>> Currently I'm testing GSRC on my PC. So, my question is: What is the
>> difference between Guix and GSRC? Regards.
>
> GSRC can be thought of as a up-to-date quarterly release of all GNU
> software. It automates the fetch/configure/build/install procedure and
> provides the occasional patch when necessary, making it easier to
> install a GNU package from source. It has light package management
> features, such as dependency resolution, but it should not be thought of
> as a package manager. GSRC only provides GNU software so external
> dependencies must be installed separately by the user.
>
> Guix, on the other hand, is a full package manager that will eventually
> form the foundation of a GNU distribution. It has far more features as
> a package manager, including some really novel ones that go above and
> beyond the usual package management functionality (better to let Ludovic
> explain). The Guix distribution will provide all of the software
> necessary to have a complete, bootable GNU system, including non-GNU
> packages. It will also handle all the fun "under-the-hood" stuff like
> system configuration and initialization, etc.
>
> Both can be used on top of an existing distro but when the Guix distro
> is ready, I will subjectively say that GSRC would be more appropriate
> for just installing a package or two on top of an existing system.
>
> There is certainly some functional overlap, and this topic has come up
> before as a result, but there remains a conceptual distinction. In
> fact, I've made changes to GSRC to reinforce this distinction
> (i.e. removing 3rd-party dependencies).
>
> I think that just about sums it up but I welcome other comments. :)
>
> Cheers,
>
> Brandon
>
Well I think that a system to easy install will be appreciated by the final
users. Especially if it helps with find/install the requirements. There are packages
like gnustep-gui or octave that can be succesfully installed with a lot of
missed functionalities if the user don't care about the recomended requirements.
And not all people out there that want use a gnu package are programmers. So
I think GSRC can help people in this way.
Regards.
Germán.
prev parent reply other threads:[~2013-05-16 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 21:59 GNU Guix 0.2 released Ludovic Courtès
2013-05-13 23:12 ` Xue Fuqiao
2013-05-15 0:56 ` Germán Arias
2013-05-15 8:53 ` Brandon Invergo
2013-05-16 7:29 ` Germán Arias [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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a909ec44336569e523a2da7a0578c87f@german-desktop \
--to=german@xelalug.org \
--cc=brandon@invergo.net \
--cc=bug-guix@gnu.org \
--cc=guile-user@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).