On Tue, Jul 10, 2018 at 08:11:24AM -0400, Jon Ringle wrote: > On Tue, Jul 10, 2018 at 3:00 AM Michael Olbrich > <[email protected]> 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 > > > <[email protected]> wrote: > > > > > > > > On Mon, Jun 18, 2018 at 08:09:20AM -0400, [email protected] 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.
Ok, I'll leave it for now. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list [email protected]
