From: "Thompson, David" <dthompson2@worcester.edu>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: RFC: Build system hacks for Guix do not belong in 'source'
Date: Thu, 5 Mar 2015 14:30:34 -0500 [thread overview]
Message-ID: <CAJ=Rwfap82OCNiTDG3jdQv3-en3qREZrnhYXbkyLDkq=YDTfMw@mail.gmail.com> (raw)
In-Reply-To: <87oao7guh3.fsf_-_@netris.org>
On Thu, Mar 5, 2015 at 1:38 PM, Mark H Weaver <mhw@netris.org> wrote:
> I don't think we should be making these kinds of changes in 'snippets'.
>
> When I ask for the source code via "guix build -S <package>", I expect
> freedom fixes and other bug fixes, and maybe even enhancements needed
> for Guix that would also work fine on other systems (e.g. adding an
> environment variable).
>
> However, the package 'source' should not include build system hacks that
> are specific to Guix and would interfere with the package functionality
> on other platforms, IMO.
I agree.
- Dave
next prev parent reply other threads:[~2015-03-05 19:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 20:54 [PATCH 1/2] gnu: Add zita-alsa-pcmi Ricardo Wurmus
2015-02-21 20:54 ` [PATCH 2/2] gnu: Add AlsaModularSynth Ricardo Wurmus
2015-02-21 21:09 ` Ricardo Wurmus
2015-02-22 20:54 ` Ricardo Wurmus
2015-02-25 14:00 ` Ludovic Courtès
2015-02-25 22:03 ` Ricardo Wurmus
2015-02-26 17:08 ` Ludovic Courtès
2015-03-01 13:49 ` Ricardo Wurmus
2015-03-01 14:59 ` Ludovic Courtès
2015-03-02 6:14 ` Mark H Weaver
2015-03-04 7:08 ` Ricardo Wurmus
2015-03-04 7:14 ` Ricardo Wurmus
2015-03-04 11:09 ` Ricardo Wurmus
2015-03-05 18:38 ` RFC: Build system hacks for Guix do not belong in 'source' Mark H Weaver
2015-03-05 19:30 ` Thompson, David [this message]
2015-03-05 22:05 ` Ludovic Courtès
2015-03-05 23:10 ` Ricardo Wurmus
2015-03-10 8:31 ` Ricardo Wurmus
2015-03-10 16:23 ` Mark H Weaver
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='CAJ=Rwfap82OCNiTDG3jdQv3-en3qREZrnhYXbkyLDkq=YDTfMw@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.