All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulius Zaleckas <paulius.zaleckas@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Anyone working on install-able packages (ipkg)
Date: Wed, 21 Apr 2010 17:06:19 +0300	[thread overview]
Message-ID: <n2sbadfd5ba1004210706ycdefbd3eva241366c36c86d83@mail.gmail.com> (raw)
In-Reply-To: <20100417023037.1bd96a69@surf>

On Sat, Apr 17, 2010 at 3:30 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> On Thu, 15 Apr 2010 16:45:04 +0200
> Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
>
> Paulius, do you have an idea on how you'd like to handle ipkg
> generation ? I have questions like :
>
> ?* How do you handle dependencies ? As of today, the dependencies in
> ? Buildroot are expressed in terms of *source* dependencies, not
> ? *binary* dependencies.

Yes, that is problem... but source dependencies are quite close to binary ones.
Bigger problem is host dependencies and here we may need to split dependencies.

> ?* What do you put in the package ? The files usually installed in
> ? $(TARGET_DIR) ? How do we modify the package infrastructure so that
> ? the package installs its files to another location ?

Yes, files usually installed into TARGET_DIR would be installed into some temp
dir and then packaged with ipkg. I have no idea how to modify
infrastructure yet.

      reply	other threads:[~2010-04-21 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 19:58 [Buildroot] Anyone working on install-able packages (ipkg) Paulius Zaleckas
2010-04-15 14:45 ` Thomas Petazzoni
2010-04-17  0:30   ` Thomas Petazzoni
2010-04-21 14:06     ` Paulius Zaleckas [this message]

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=n2sbadfd5ba1004210706ycdefbd3eva241366c36c86d83@mail.gmail.com \
    --to=paulius.zaleckas@gmail.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 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.