From: Laurent Bercot <ska-dietlibc@skarnet.org>
To: musl@lists.openwall.com
Subject: Re: Bits deduplication: current situation
Date: Mon, 25 Jan 2016 11:46:30 +0100 [thread overview]
Message-ID: <56A5FD06.2060908@skarnet.org> (raw)
In-Reply-To: <20160125035925.GA2288@brightrain.aerifal.cx>
On 25/01/2016 04:59, Rich Felker wrote:
> A possible compromise is to highly abstract these things at the musl
> source level, but generate flat bits files to install, or even flatten
> the headers completely to remove bits so that all definitions are
> inline and explicit in the top-level headers.
Whatever you choose to do, my position is that clarity of the source is
more important than clarity of the installed files. Maintenance effort
goes to the source, not to the installed files. Users who peek at
installed headers to know what's going on will be able to figure it out,
and if they're not, they can always grab the musl source.
Independently from that, I find it nice, when faced with a tree of
headers, to be able to see at a glance what can be copied as is and
what has been generated (and thus cannot be safely modified or reused
elsewhere). So I'm in favor of a separate bits, no matter what the
files under it look like.
--
Laurent
next prev parent reply other threads:[~2016-01-25 10:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 3:59 Rich Felker
2016-01-25 8:08 ` Natanael Copa
2016-01-25 17:17 ` Rich Felker
2016-01-25 10:46 ` Laurent Bercot [this message]
2016-01-25 14:56 ` Ward Willats
2016-01-25 15:37 ` Szabolcs Nagy
2016-01-25 19:22 ` Dan Gohman
2016-01-25 21:00 ` Rich Felker
2016-01-25 21:32 ` Szabolcs Nagy
2016-01-26 5:03 ` Dan Gohman
2016-01-26 10:18 ` Szabolcs Nagy
2016-01-26 15:16 ` Dan Gohman
2016-01-26 20:26 ` Szabolcs Nagy
2016-01-26 20:17 ` 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=56A5FD06.2060908@skarnet.org \
--to=ska-dietlibc@skarnet.org \
--cc=musl@lists.openwall.com \
/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).