All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: "Dr. Michael Lauer" <mickey@vanille-media.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: dbg packages (was: org.oe.dev wireshark: fix -dbg)
Date: Tue, 10 Jul 2007 01:52:47 +0300	[thread overview]
Message-ID: <96699408.20070710015247@gmail.com> (raw)
In-Reply-To: <126613333.20070709215755@vanille-media.de>

Hello Dr.,

Monday, July 9, 2007, 10:57:55 PM, you wrote:

> koen commit wrote:
>> wireshark: fix -dbg
> [...]
>> +
>> +FILES_${PN}-dbg += "${libdir}/wireshark/plugins/${PV}/.debug"
>> +
>> +

> We keep adding this stuff more and more -- since more and more
> packages go from a monolithic state to an extensible -- and
> I don't like having to specify this all over. Can't we get the dbg
> package to pick up all .debug directories automatically?

  That's what I was thinking for some time now too. It's good that
bitbake is expressive enought that we *can* so that with its generic means
like FILES, but doing that again and again instead once and for all is
really boring.

  And there's another issue here - empty .debug directories throught
the rootfs. This one is actually more complex, as empty directories
are there because of package-write task's workings, and sometimes we
want them, sometimes not, so it's unclear how to handle that issue. At
least we for sure don't want empty .debug/'s.

> Regards,

> :M:



-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




      parent reply	other threads:[~2007-07-09 22:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1I7yE2-0000V0-1x@linuxtogo.org>
2007-07-09 19:57 ` dbg packages (was: org.oe.dev wireshark: fix -dbg) Dr. Michael Lauer
2007-07-09 20:11   ` dbg packages Koen Kooi
2007-07-09 22:05     ` Rolf Leggewie
2007-07-10  9:21       ` Dr. Michael Lauer
2007-07-10 10:51         ` Richard Purdie
2007-07-10 12:54           ` Paul Sokolovsky
2007-07-09 22:52   ` Paul Sokolovsky [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=96699408.20070710015247@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=mickey@vanille-media.de \
    --cc=openembedded-devel@lists.openembedded.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.