From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] initramfs-tools: Restore package
Date: Tue, 10 Jul 2018 08:11:24 -0400 [thread overview]
Message-ID: <CAMwGMjypjc3NJeZVaT8F_hW76AFjwFgNTdP39T7UK6cB4vXapQ@mail.gmail.com> (raw)
In-Reply-To: <20180710070034.5gqok4cwjukgkwec@pengutronix.de>
On Tue, Jul 10, 2018 at 3:00 AM Michael Olbrich
<m.olbrich@pengutronix.de> wrote:
>
> On Fri, Jul 06, 2018 at 10:27:46PM -0400, Jon Ringle wrote:
> > On Tue, Jun 19, 2018 at 10:45 AM Michael Olbrich
> > <m.olbrich@pengutronix.de> wrote:
> > >
> > > On Mon, Jun 18, 2018 at 08:09:20AM -0400, jon@ringle.org wrote:
> > > > +if INITRAMFS_TOOLS
> > > > +
> > > > +config INITRAMFS_SPEC
> > >
> > > Is this spec stuff something you need? I actually missed this when I
> > > removed all the other pieces, so I'd like to remove this as well.
> > >
> > > This seems to be just a indirection to install files. I'd prefer normal
> > > packages for this.
> >
> > I can remove it. However, could we keep the $(call install_spec ...)
> > macro intact so that at least I can create a rule file in my local
> > project that can use this:?
>
> What can you do with install_spec that cannot be handled with install_copy
> etc.?
Everything that install_spec does can be handled with install_copy,
install_link and install_node.
However, this is more of a preference in how I want to handle
maintenance and installing of some project specific files that don't
fit nicely into any specific package.
Regards,
-Jon
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-07-10 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 12:09 jon
2018-06-19 14:45 ` Michael Olbrich
2018-07-07 2:27 ` Jon Ringle
2018-07-10 7:00 ` Michael Olbrich
2018-07-10 12:11 ` Jon Ringle [this message]
2018-07-10 12:45 ` Michael Olbrich
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=CAMwGMjypjc3NJeZVaT8F_hW76AFjwFgNTdP39T7UK6cB4vXapQ@mail.gmail.com \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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