Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS

Bruce Ashfield

On Thu, Jan 19, 2017 at 3:17 PM, Otavio Salvador <otavio.salvador@...> wrote:
On Thu, Jan 19, 2017 at 5:47 PM, Patrick Ohly <patrick.ohly@...> wrote:
> On Wed, 2017-01-18 at 21:26 +0000, Richard Purdie wrote:
>> On Wed, 2017-01-18 at 11:57 -0600, Mark Hatle wrote:
>> > > Does that make it clearer why we need this?
>> > I certainly understand it more.. I'm just struggling with how to
>> > explain when
>> > someone would need this or not, to someone who hasn't hit one of the
>> > extraction
>> > problems.   I think that is by far my biggest remaining concern, how
>> > to make
>> > sure people can understand they need to do this and when...
>> The rules in some ways are simple, it comes down to:
>> """
>> If your postinstall can execute at rootfs creation time rather than on
>> target but depends on a native tool in order to execute, you need to
>> list that tool in PACKAGE_WRITE_DEPENDS.
>> """
> Looking at this description, it is not at all clear to me why the
> variable is named PACKAGE_WRITE_DEPENDS. From the description, the
> things listed in it are dependencies of do_rootfs, not of
> do_package_write_*, even if it happens to be implemented that way.
> I like PS_NATIVE_DEPENDS better. Just my 2 cents.

PACKAGE_SCRIPTS_DEPENDS maps better to what they are intended to be
used for, I think.

I tend to agree with the expanded "package", I keep reading "PS" as any
number of random things ... including "professional services".



Otavio Salvador                             O.S. Systems
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
Openembedded-architecture mailing list

"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"

Join { to automatically receive all group messages.