Hi Khem,
On Fri, Jun 1, 2018 at 1:11 PM, Khem Raj wrote:
> On 5/31/18 1:06 PM, Trevor Woerner wrote:
> > Instead of installing an entire recipe's build output (i.e. ${D}), allow
> the
> > user to optionally specify a package from said recipe to be installed
> > exclusively (i.e. ${PKGDEST}/).
>
On Tuesday, 5 June 2018 10:59:07 AM NZST Paul Eggleton wrote:
> I will note that a small issue with your patch is that if you do use --
> package
> you can no longer just use devtool build to build what you need to deploy,
> since that only builds up to do_populate_sysroot / do_packagedata. This
Hi Paul,
I was hoping you'd notice and provide feedback :-D
On Tue 2018-06-05 @ 10:59:07 AM, Paul Eggleton wrote:
> > I checked at the time, but I'm not 100% sure now, but I believe if one
> > deploys two packages from one recipe, the on-target file gets appended. But
> > now I'm not 100% sure, s
Hi Trevor,
On Friday, 1 June 2018 2:23:59 PM NZST Trevor Woerner wrote:
> Earlier today I was working on recipes for some software which recently
> added the feature to dlopen() one of a couple shared objects based on
> various conditions. But instead of dlopen()'ing the SONAME, they were
> dlopen
On Fri, Jun 1, 2018 at 7:58 AM, Trevor Woerner wrote:
> On Thu, May 31, 2018 at 11:07 PM, Andre McCurdy wrote:
>> On Thu, May 31, 2018 at 7:23 PM, Trevor Woerner
>> wrote:
>>
>> I wonder whether the default behaviour should just be to not deploy
>> files from the -dev package?
>>
>
> That would
On 5/31/18 1:06 PM, Trevor Woerner wrote:
> Instead of installing an entire recipe's build output (i.e. ${D}), allow the
> user to optionally specify a package from said recipe to be installed
> exclusively (i.e. ${PKGDEST}/).
>
Thinking of developer's workflow, it might be needed to be able to
i
On Thu, May 31, 2018 at 11:07 PM, Andre McCurdy wrote:
> On Thu, May 31, 2018 at 7:23 PM, Trevor Woerner
> wrote:
>
> I wonder whether the default behaviour should just be to not deploy
> files from the -dev package?
>
>
That would certainly be an improvement. But it still wouldn't make sense to
On Thu, May 31, 2018 at 7:23 PM, Trevor Woerner wrote:
> Hi Andre, thanks for taking an interest!
>
> On Thu, May 31, 2018 at 6:22 PM, Andre McCurdy wrote:
>>
>> On Thu, May 31, 2018 at 1:06 PM, Trevor Woerner
>> wrote:
>> > Instead of installing an entire recipe's build output (i.e. ${D}), allo
Hi Andre, thanks for taking an interest!
On Thu, May 31, 2018 at 6:22 PM, Andre McCurdy wrote:
> On Thu, May 31, 2018 at 1:06 PM, Trevor Woerner
> wrote:
> > Instead of installing an entire recipe's build output (i.e. ${D}), allow
> the
> > user to optionally specify a package from said recipe
On Thu, May 31, 2018 at 1:06 PM, Trevor Woerner wrote:
> Instead of installing an entire recipe's build output (i.e. ${D}), allow the
> user to optionally specify a package from said recipe to be installed
> exclusively (i.e. ${PKGDEST}/).
I'm not a big devtool user myself, but I'm curious about
Instead of installing an entire recipe's build output (i.e. ${D}), allow the
user to optionally specify a package from said recipe to be installed
exclusively (i.e. ${PKGDEST}/).
Signed-off-by: Trevor Woerner
---
scripts/lib/devtool/deploy.py | 26 ++
1 file changed, 18 i
11 matches
Mail list logo
