From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] svgtiny: update source url
Date: Mon, 5 Jan 2015 17:34:02 +0100 [thread overview]
Message-ID: <20150105173402.41315fcb@free-electrons.com> (raw)
In-Reply-To: <CAHkwnC_aRYSYQE-b_rdOCoe5u9U+Stq1VZ6nZEdmjkv+nArQeg@mail.gmail.com>
Dear Fabio Porcedda,
On Mon, 5 Jan 2015 15:29:06 +0100, Fabio Porcedda wrote:
> Yes, the repository is:
> http://git.netsurf-browser.org/buildsystem.git/
>
> But those sources alone do nothing, the build and install target of
> this package will be empty.
> Also to use those files at least a symbolic link must be added to the
> libsvgtiniy directory to access buildsystem.git files.
> Considering all of this it is still preferably worth adding a separate
> package for those files?
Yes, I personally believe it's preferable to have a separate package.
Create a netsurf-buildsystem package, which installs those files to
$(STAGING_DIR)/usr/share/netsurf-buildsystem/ for example. Then
libsvgtiny would depend on netsurf-buildsystem, and in a post-extract
hook, create the necessary symlink.
Not sure if netsurf-buildsystem should be a target package (and install
its stuff to staging) or a host package (and install its stuff to
HOST_DIR).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-05 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 11:02 [Buildroot] [PATCH v3] svgtiny: update source url Fabio Porcedda
2015-01-05 13:15 ` Thomas Petazzoni
2015-01-05 14:29 ` Fabio Porcedda
2015-01-05 16:34 ` Thomas Petazzoni [this message]
2015-01-07 16:51 ` Fabio Porcedda
2015-01-07 20:18 ` Thomas Petazzoni
2015-01-09 7:15 ` Fabio Porcedda
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=20150105173402.41315fcb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox