Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: dbg packages
Date: Mon, 09 Jul 2007 21:11:31 +0100	[thread overview]
Message-ID: <f6u4pj$fk0$1@sea.gmane.org> (raw)
In-Reply-To: <126613333.20070709215755@vanille-media.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dr. Michael Lauer schreef:
> 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?

In this case I'd say "make wireshark even more granular by subpackaging its 2 shlibs and
plugins", which would not want every .debug directory in ${PN}-dbg.

In the general case I'm not sure if we want something automagically added to ${PN}-dbg or
not, since it is likely to be wrong in a lot of cases. So I'm not sure if something
automagically would cause more or less work for packages I want to add/maintain/fix.

What I would like to see implemented is some heuristic that puts .debug/<foo> in the -dbg
(sub)package that is named after the (sub)package that has <foo> (e.g. create
wireshark-plugin-<foo>-dbg automagically after finding <foo> in wireshark-plugin-<foo>).

Same goes for lib<foo>-dev automagically getting lib<foo>.{so,a,la,pc}, headers will have
to get sorted by hand.

Packaging is tedious, but let's not automate doing the wrong thing ;)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGkpZzMkyGM64RGpERAnhTAJsGakQCTjzec/sLVBoA9Zb/S6D7VwCdE8Qz
pnvest3WtETPsF4K93kWHWI=
=FrV+
-----END PGP SIGNATURE-----




  reply	other threads:[~2007-07-09 20:17 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   ` Koen Kooi [this message]
2007-07-09 22:05     ` dbg packages 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   ` dbg packages (was: org.oe.dev wireshark: fix -dbg) Paul Sokolovsky

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='f6u4pj$fk0$1@sea.gmane.org' \
    --to=koen@dominion.kabel.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox