Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: QA for intentionally unpackaged files
Date: Wed, 9 May 2007 14:37:09 +0300	[thread overview]
Message-ID: <818235002.20070509143709@gmail.com> (raw)
In-Reply-To: <4641AFCB.6080203@dominion.kabel.utwente.nl>

Hello Koen,

Wednesday, May 9, 2007, 2:26:03 PM, you wrote:


> Junqian Gordon Xu schreef:
>> Koen Kooi wrote:
>>> Or we could patch package.bbclass[1] to do:
>>>
>>> PACKAGES += "${PN}-leftovers"
>>> FILES_${PN}-leftovers = "/"
>>>
>>> I'm not sure if that works, but if it does, we would be able to spot leftovers more easily
>>> by looking at deploy.
>> 
>> Again, how do you know which one is "intentionally" left-over vs. which 
>> one is not?

> I can't think of a valid reason for not packaging files.

        busybox doesn't package symlinks, as update-alternative
recreates them on install.


        But I agree that catch-all package is better idea than another
adhoc var. Except that we probably should add ${PN}-unshipped and
${PN}-leftovers to distinguish those intentional vs missed cases.

> regards,

> Koen

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




  reply	other threads:[~2007-05-09 11:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09  2:25 QA for intentionally unpackaged files Junqian Gordon Xu
2007-05-09  9:38 ` Paul Sokolovsky
2007-05-09 10:31   ` Michael Krelin
2007-05-09 10:42     ` Koen Kooi
2007-05-09 10:57       ` Junqian Gordon Xu
2007-05-09 11:26         ` Koen Kooi
2007-05-09 11:37           ` Paul Sokolovsky [this message]
2007-05-09 11:51             ` Michael Krelin
2007-05-09 11:43       ` Michael Krelin
2007-05-09 10:48   ` Junqian Gordon Xu

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=818235002.20070509143709@gmail.com \
    --to=pmiscml@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox