Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 17 Jul 2018 09:56:59 +0200
From: ardi <ardillasdelmonte@...il.com>
To: musl@...ts.openwall.com
Subject: Re: Timeline for 1.1.20?

On Mon, Jul 16, 2018 at 7:20 PM, Rich Felker <dalias@...c.org> wrote:
> On Wed, Jul 11, 2018 at 09:17:01AM +0200, ardi wrote:
>> Hi!
>>
>> Is there a timeline for the 1.1.20 release? I'm starting a project,
>> and I'd find it very convenient to know if 1.1.20 will be released
>> this month, or if 1.1.19 is going to be kept as the current release
>> for some months to come.
>
> I don't have a date in mind, but letting it get drawn out for "some
> months" again is definitely not something I want to have happen.
> There's definitely enough time left in this month that a release
> before the end should be possible. Assistance with testing/checks for
> regressions would help a lot.

I'm not the best one for doing testing, as I don't have any previous
code based on musl, and moreover, my way of using it is going to be
non-obvious/marginal, as I'm working in being OS-independent, as I
wrote in the list months ago. There's a possibility that I end up
combining code from newlib and musl, but that's not certain at this
moment (the only certain thing for the moment is that musl has
everything I need, including a complete ELF dynamic linker/loader, and
that newlib follows the approach I want -syscall isolation- but it's
less complete and has no linker/loader). So, I need to dig deeply at
building both libraries, and finding my way during the process.

Said this, I'm starting my efforts through an Alpine Linux VM (for
obvious reasons, as musl is default there, and llvm is also there,
which is the compiler suite I use), so I'll be happy to test in that
VM any 1.1.20 release candidates you prepare, although I assume that
Alpine will be a platform for which you'll have testers already.

Thanks!

ardi

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ