From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9187 Path: news.gmane.org!not-for-mail From: Laurent Bercot Newsgroups: gmane.linux.lib.musl.general Subject: Re: Bits deduplication: current situation Date: Mon, 25 Jan 2016 11:46:30 +0100 Message-ID: <56A5FD06.2060908@skarnet.org> References: <20160125035925.GA2288@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1453718808 27947 80.91.229.3 (25 Jan 2016 10:46:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 25 Jan 2016 10:46:48 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9200-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jan 25 11:46:47 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1aNefV-0005Kj-KZ for gllmg-musl@m.gmane.org; Mon, 25 Jan 2016 11:46:45 +0100 Original-Received: (qmail 32542 invoked by uid 550); 25 Jan 2016 10:46:42 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 32520 invoked from network); 25 Jan 2016 10:46:41 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 In-Reply-To: <20160125035925.GA2288@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:9187 Archived-At: 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