[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121120050940.GA13916@brightrain.aerifal.cx>
Date: Tue, 20 Nov 2012 00:09:40 -0500
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Revisiting 1.0 wishlist
About 18 months ago, shortly after the initial public release of musl,
I posted a wishlist of what I thought it would take to consider musl
to have reached "1.0" quality. The other day I was revisiting that,
and thought I'd post a summary of my thoughts to the list as a
starting point for further discussion.
Completed goals:
- coverage for all of C99 and POSIX base and supported option groups
- character class handling sync'd to current Unicode
- dynamic loading (except in static-linked apps)
- C++ support
In addition, significant progress has been made on the open-ended
goals of application compatibility and ability to load/run some
glibc-linked binaries (applications and libraries). Part of the goal
originally stated in the wishlist was to determine a collection of
"important" applications and ensure compatibility against them. I
think now would be a good time to start doing that. Perhaps LFS (Linux
>From Scratch) might make a good base set to start with, especially
since lots of people building their own systems who might use musl
will be starting with LFS as a guide. We could add and remove some
packages from the list as desired.
Aside from yet-to-be-defined compatibility goals, the only thing
missing from musl that was in the original 1.0 wishlist is
documentation.
There is also one other goal I introduced later, on which I think 1.0
needs to depend: support for a to-be-determined set of additional
legacy character encodings in iconv. At the very least, the major
legacy encodings for Korean and Traditional Chinese should be
included, and it may also be desirable to add support for stateful
encodings (ISO-2022). Aside from these, I believe all encodings
important for supporting legacy data on the web, in email, etc. are
supported.
That's about it for now. As usual, comments are welcome.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
