all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Installing Guix easily on other distros
Date: Thu, 14 Apr 2016 18:58:08 +0200	[thread overview]
Message-ID: <87a8kwm8kf.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=Rwfb-rGbAD0RQOydjwL6kH04Kgxn2G999sLdNkbU_GXnxGQ@mail.gmail.com> (David Thompson's message of "Thu, 14 Apr 2016 10:39:41 -0400")

"Thompson, David" <dthompson2@worcester.edu> skribis:

> On Thu, Apr 14, 2016 at 10:28 AM, Ricardo Wurmus
> <ricardo.wurmus@mdc-berlin.de> wrote:
>>
>> Thompson, David <dthompson2@worcester.edu> writes:
>>
>>> On Thu, Apr 14, 2016 at 9:51 AM, Hartmut Goebel
>>> <h.goebel@crazy-compilers.com> wrote:
>>>> Hi,
>>>>
>>>> today on irc, there was discussion about that Guix should be easily
>>>> installable and manageable in other distros being higher priority. This
>>>> could attract more users to ry out Guix. So I created a draft .spec-file
>>>> for building and installing Guix o RPM-based systems like Fedora.
>>>>
>>>> Maybe someone using Fedora may want to add a package request in their
>>>> bug-tracker. I already did for Mageia.
>>>
>>> This has come up several times, and I agree that we should provide
>>> packages for popular GNU/Linux distributions.  However, Guix *cannot*
>>> be made available in many distros official repositories (most notably
>>> Debian and Fedora) because Guix violates their policies, such as:
>>>
>>> - Software must conform to the Filesystem Hierarchy Standard
>>> (violation: Guix introduces the /gnu directory)
>>> - Software must be bootstrapped from source (violation: Guix requires
>>> a set of bootstrap binaries that *cannot* be replaced by the distro
>>> without changing the hashes of every package, effectively preventing
>>> them from receiving binaries from hydra.gnu.org)
>>>
>>> Guix is at odds with other distros because it is a distro itself.  So,
>>> I think what would be best is for users of these distros to host Guix
>>> packages in popular places for third-party packages, like Arch's AUR
>>> or Fedora's COPR:
>>>
>>> https://aur.archlinux.org/packages/guix/
>>> https://copr.fedorainfracloud.org/coprs/lantw44/guix/
>>>
>>> What would be even better is if people *told us* when they made a
>>> package.  I learned about these indirectly, long after they were
>>> originally available.
>>
>> Could we add the .spec, PKGBUILD, and debian files to the Guix
>> repository?  I know of many projects that include the package manifests
>> to simplify building packages for major distributions.
>>
>> An advantage would be that we knew about these files and users wouldn’t
>> have to search around for the latest package sources.
>
> That sounds like a good idea.  I would welcome patches for such things.

Seconded (as long as it’s one or two files per distro.)

Ludo’.

  reply	other threads:[~2016-04-14 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 13:51 Installing Guix easily on other distros Hartmut Goebel
2016-04-14 14:02 ` Cyril Roelandt
2016-04-14 14:07 ` Thompson, David
2016-04-14 14:28   ` Ricardo Wurmus
2016-04-14 14:39     ` Thompson, David
2016-04-14 16:58       ` Ludovic Courtès [this message]
2016-04-14 17:00     ` Mathieu Lirzin
2016-04-14 17:48       ` Hartmut Goebel

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

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

  git send-email \
    --in-reply-to=87a8kwm8kf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dthompson2@worcester.edu \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.