From: Rich Felker <dalias@libc.org>
To: Weldon Goree <weldon@langurwallah.org>
Cc: musl@lists.openwall.com
Subject: Re: Packaging: Slackware
Date: Fri, 18 Jul 2014 15:53:59 -0400 [thread overview]
Message-ID: <20140718195359.GY17402@brightrain.aerifal.cx> (raw)
In-Reply-To: <53C8E3A2.20206@langurwallah.org>
On Fri, Jul 18, 2014 at 02:36:42PM +0530, Weldon Goree wrote:
> I'm asking on the Slackbuilds list, too, but just to cover all bases:
> anybody's toes going to get stepped on if I go forward with a slackbuild
> of musl and submit it? I don't intend to touch 1.1.X at all and only
> package the latest 1.0.X.
>
> (And, on that note, Rich, what's the support expectation lifetime for
> 1.0.X, if that's defined?)
There was a thread about the usefulness and lifetime of the 1.0.x
series about a month ago. The interest level was very low so my plan
based on that was to stick to only important bug fixes, and phase it
out within the next 4-6 months. But to do that, I'm looking for ways
to help distros/users integrate 1.1.x releases without being "forced
to upgrade" earlier than they want to in order to get bugfixes.
If you have thoughts on why you don't want to use 1.1.x, hearing those
would be helpful in further planning how to proceed with 1.0.x.
Rich
next prev parent reply other threads:[~2014-07-18 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 9:06 Weldon Goree
2014-07-18 19:53 ` Rich Felker [this message]
2014-07-19 2:54 ` Weldon Goree
2014-07-21 2:48 ` Rich Felker
2014-07-21 14:04 ` James B
2014-07-21 14:15 ` Rich Felker
2014-07-21 14:42 ` Weldon Goree
2014-07-21 14:50 ` Rich Felker
2014-09-06 16:10 ` Rich Felker
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=20140718195359.GY17402@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=weldon@langurwallah.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.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).