From: ng0 <ng0@libertad.pw>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: cargo-build-system: cargo-build-flags: --cfg=unix in package recipe
Date: Wed, 04 Jan 2017 13:44:25 +0000 [thread overview]
Message-ID: <87shozueh2.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170104142601.2b678a6a@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> writes:
> I'm against packaging unstable stuff. We would be packaging a moving target where everything breaks every day. Let's not.
>
> There's a reason there are stable releases (of anything): there's (supposed to be) a (social) guarantee that the API doesn't change in incompatible ways.
>
> If a library doesn't work in a stable release, upstream has to get it to work. Simple as that.
> Otherwise it just shouldn't be packaged. People can still use cargo to install it so we aren't preventing anyone from using it.
>
> That said, there could be a rustc-devel package (only for rustc). Other packages, people should be on their own.
>
> Please, let's not make unstable stable by decree. If anything, upstream should just release more stuff as stable (if it's stable) :P
>
I agree. I think it's not a solution we should try unless we
haven't tried every possible solution out there.
--
♥Ⓐ ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org
next prev parent reply other threads:[~2017-01-04 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 1:10 cargo-build-system: cargo-build-flags: --cfg=unix in package recipe Danny Milosavljevic
2017-01-03 1:46 ` Danny Milosavljevic
2017-01-03 2:32 ` Danny Milosavljevic
2017-01-03 10:57 ` David Craven
2017-01-03 11:55 ` Danny Milosavljevic
2017-01-04 11:38 ` ng0
2017-01-04 11:45 ` David Craven
2017-01-04 13:26 ` Danny Milosavljevic
2017-01-04 13:44 ` ng0 [this message]
2017-01-03 20:10 ` Danny Milosavljevic
2017-01-03 11:19 ` ng0
2017-01-03 12:02 ` Danny Milosavljevic
2017-01-03 14:09 ` ng0
2017-01-03 14:38 ` David Craven
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=87shozueh2.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--cc=dannym@scratchpost.org \
--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).