All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Woronicz, Bartosz ( NSN - PL/Wroclaw)" <bartosz.woronicz@nokia.com>
To: "EXT Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Where should I append Yocto bitbake task to create work folder symlink ?
Date: Wed, 3 Feb 2016 15:16:01 +0100	[thread overview]
Message-ID: <56B20BA1.2060004@nokia.com> (raw)
In-Reply-To: <CAJTo0LayhHP7wbcbLf7TOu8e=6-ERg90VdJu_Av9EfmBBFEmAg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]


On 03.02.2016 11:28, EXT Burton, Ross wrote:
>
> On 3 February 2016 at 10:13, Woronicz, Bartosz ( NSN - PL/Wroclaw) 
> <bartosz.woronicz@nokia.com <mailto:bartosz.woronicz@nokia.com>> wrote:
>
>     Let's say I have my package at
>
>     host-64/tmp/work/x86_64-poky-linux/mypackage/1.2.3-r4/
>
>     I would like to have symlink created
>
>         host-64/tmp/work/x86_64-poky-linux/mypackage/latest -> 1.2.3-r4/
>
>     each time the new version is fetched and unpacked. How can I
>     achieve that ? Which class, task should I append, extend ?
>
>
> One way would be to create a new task that comes after unpack and 
> creates the symlink.
>
> You may be interested in the rm_old_work class that can remove old 
> work trees so there's only ever one work tree, and I believe due to 
> how master does sysroot cleanup there's only ever one version in work/ 
> now.
>
> Ross
But I need to the sysroot cleanup deliberately, right ?


----

Kind regards,
Bartosz Woronicz
Engineer, Software Configuration (SCM)
NSN - PL/Wroclaw



[-- Attachment #2: Type: text/html, Size: 2574 bytes --]

  reply	other threads:[~2016-02-03 14:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 10:13 Where should I append Yocto bitbake task to create work folder symlink ? Woronicz, Bartosz ( NSN - PL/Wroclaw)
2016-02-03 10:28 ` Burton, Ross
2016-02-03 14:16   ` Woronicz, Bartosz ( NSN - PL/Wroclaw) [this message]
2016-02-03 15:40     ` Burton, Ross
2016-02-04 11:03       ` Woronicz, Bartosz ( NSN - PL/Wroclaw)
2016-02-03 11:05 ` Maciek Borzecki
2016-02-04 11:07   ` Woronicz, Bartosz ( NSN - PL/Wroclaw)
2016-02-08 13:20     ` Woronicz, Bartosz ( NSN - PL/Wroclaw)
2016-02-08 13:44       ` Maciek Borzecki
2016-02-09  8:37         ` Woronicz, Bartosz ( NSN - PL/Wroclaw)
2016-02-09  9:10           ` Burton, Ross
2016-02-09 13:51             ` Woronicz, Bartosz ( NSN - PL/Wroclaw)
2016-02-09 13:56               ` Burton, Ross
2016-02-10 14:00                 ` Woronicz, Bartosz ( NSN - PL/Wroclaw)

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=56B20BA1.2060004@nokia.com \
    --to=bartosz.woronicz@nokia.com \
    --cc=ross.burton@intel.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.