From: James B <jamesbond3142@gmail.com>
To: musl@lists.openwall.com
Cc: Rich Felker <dalias@libc.org>, Weldon Goree <weldon@langurwallah.org>
Subject: Re: Packaging: Slackware
Date: Mon, 21 Jul 2014 21:04:10 +0700 [thread overview]
Message-ID: <20140721210410.46dfb8b3334acb999e7bd70f@gmail.com> (raw)
In-Reply-To: <20140721024834.GM17402@brightrain.aerifal.cx>
On Sun, 20 Jul 2014 22:48:34 -0400
Rich Felker <dalias@libc.org> wrote:
>
> Knowing a little bit more about the goal of the slackbuild (and what
> exactly a "slackbuild" is) might help me make a better recommendation
> and assess whether extending the life of the 1.0.x branch is
> worthwhile for what you're doing.
"Slackbuild" is a build recipe, just like RPM spec file or Arch PKGBUILD.
There is a website called slackbuilds.org which collects thirdparty slackbuilds (ie build recipes that are not part of official Slackware repository) for others to use. Slackbuilds.org tend to group slackbuilds following Slackware official releases (there is a group of slackbuilds targetted for Slackware 13, Slack 14, Slack 14.1, etc etc).
I'm not speaking on behalf of Weldon but I guess this would be where the musl slackbuild will end up.
cheers!
--
James B <jamesbond3142@gmail.com>
next prev parent reply other threads:[~2014-07-21 14:04 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
2014-07-19 2:54 ` Weldon Goree
2014-07-21 2:48 ` Rich Felker
2014-07-21 14:04 ` James B [this message]
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=20140721210410.46dfb8b3334acb999e7bd70f@gmail.com \
--to=jamesbond3142@gmail.com \
--cc=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).