From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 02/11] per-package .users and .files lists
Date: Tue, 24 Mar 2015 22:43:57 +0200 [thread overview]
Message-ID: <20150324204357.GA4906@vostro> (raw)
In-Reply-To: <550ED31D.6040902@mind.be>
Sun, Mar 22, 2015 at 03:35:09PM +0100, Arnout Vandecappelle wrote:
> > With this patch, the data is stored outside of make, possibly
> > allowing one make invocation per package .mk file in the future.
>
> So, is there any reason left to move USERS and PERMS to a file?
No, none at present, so I'm dropping this idea completely.
> It has one big disadvantage: it spreads out the package logic over different
> files. We currently only have a separate file for the hashes, and that was
> probably a bad idea to begin with (as witnessed by the many version bumps that
> forget to update the hash file).
Ok, that was for the large part to match current .hash handling.
I wonder if it makes sense to move hashes into .mk files then, Arch-style.
next prev parent reply other threads:[~2015-03-24 20:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 18:26 [Buildroot] [RFC 00/11] common init infrastructure Alex Suykov
2015-03-21 18:27 ` [Buildroot] [RFC 01/11] common service startup files Alex Suykov
2015-03-21 23:57 ` Arnout Vandecappelle
2015-03-22 12:39 ` Alex Suykov
2015-03-22 13:49 ` Arnout Vandecappelle
2015-03-22 13:51 ` Arnout Vandecappelle
2015-03-22 11:45 ` Yann E. MORIN
2015-03-22 13:41 ` Arnout Vandecappelle
2015-03-21 18:27 ` [Buildroot] [RFC 02/11] per-package .users and .files lists Alex Suykov
2015-03-22 14:35 ` Arnout Vandecappelle
2015-03-24 20:43 ` Alex Suykov [this message]
2015-03-21 18:28 ` [Buildroot] [RFC 03/11] init/finalize script Alex Suykov
2015-03-21 18:29 ` [Buildroot] [RFC 04/11] help entries for Init system config menu Alex Suykov
2015-03-21 18:30 ` [Buildroot] [RFC 05/11] bare bb init configuration Alex Suykov
2015-03-21 18:30 ` [Buildroot] [RFC 06/11] ptp: new init infrastructure Alex Suykov
2015-03-21 18:31 ` [Buildroot] [RFC 07/11] upmpcli: " Alex Suykov
2015-03-21 18:31 ` [Buildroot] [RFC 08/11] acpid: " Alex Suykov
2015-03-21 18:32 ` [Buildroot] [RFC 09/11] am33x-cm3: " Alex Suykov
2015-03-21 18:34 ` [Buildroot] [RFC 10/11] postgresql: " Alex Suykov
2015-03-21 18:35 ` [Buildroot] [RFC 11/11] openvpn: " Alex Suykov
2015-03-21 20:41 ` [Buildroot] [RFC 00/11] common " Arnout Vandecappelle
2015-03-22 10:30 ` Alex Suykov
2015-03-22 11:28 ` Yann E. MORIN
2015-03-22 13:23 ` Alex Suykov
2015-03-22 13:34 ` Arnout Vandecappelle
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=20150324204357.GA4906@vostro \
--to=alex.suykov@gmail.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox