From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: dbg packages
Date: Tue, 10 Jul 2007 00:05:52 +0200 [thread overview]
Message-ID: <f6ubg3$97c$1@sea.gmane.org> (raw)
In-Reply-To: <f6u4pj$fk0$1@sea.gmane.org>
Koen Kooi wrote:
> Packaging is tedious, but let's not automate doing the wrong thing ;)
I certainly agree with the general statement. But I wonder if in this
case it would not be OK to have just one big -dbg package per bb file
even if there are more subpackages. Going granular is certainly nice
but I wonder if just having a dbg package suffices even if contains more
than necessary. I guess the -dbg packages should not be necessary most
of the time.
My vote would go for "bigger size" if it means "easier packaging right
now instead of later" unless that entails "something breaks".
next prev parent reply other threads:[~2007-07-09 22:11 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 [this message]
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='f6ubg3$97c$1@sea.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--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 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.