From: Lars Larsen <lars@visionweeding.com>
To: poky@yoctoproject.org
Subject: can I excute a "git config" before do_fetch ? to avoid HDD bloating
Date: Thu, 12 Jan 2017 13:09:39 +0100 [thread overview]
Message-ID: <58777203.7010006@visionweeding.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
Dear Poky world
I wonder if it is possible to achieve the following ?
We have some home cooked , git controlled modules, that expose a public API.
By company convention, public interfaces must be located in a lib/
directory within the module.
It would be nice to checkout only the interface stuff in lib/, without
polluting the HDD with the entire module, when we only need the
interface files.
*By hand it is easy:*
If a developer want to use this public interface, he/she will use the
git sparse-checkout feature, to avoid checking out the entire module -
executing these commands will checkout only the lib directory
|mkdir <repo> cd <repo> git init git remote add -f origin <url> ||git config core.sparseCheckout true ||echo "lib/">>.git/info/sparse-checkout |
git pull origin <branch> / checkout will the only affect the lib/
directory *How to do from a recipe ? * I want to make a poky-recipe for
the public interface, so API users can specify DEPENDS it their
recipes So do I make my own class that inserts a buildstep before
do_unpack ? Ideas and concrete examples will be highly appreciated. Of
course I can choose to let the API Recipe checkout the parent project in
it's entirety, and the do it's personal build magic in on the lib/ only.
No real disasters will happen, other that waisting some MB's on my
colleagues HDD. BR Lars Larsen
--
Best Regards
Lars Larsen
F.Poulsen Engineering Aps
Tjørnager 16
4330 Hvalsø
Denmark
+45 29802784
www.visionweeding.com
[-- Attachment #2: Type: text/html, Size: 5280 bytes --]
reply other threads:[~2017-01-12 12:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=58777203.7010006@visionweeding.com \
--to=lars@visionweeding.com \
--cc=poky@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.