All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Krelin <hacker@klever.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: QA for intentionally unpackaged files
Date: Wed, 09 May 2007 13:43:32 +0200	[thread overview]
Message-ID: <4641B3E4.1020107@klever.net> (raw)
In-Reply-To: <4641A5A2.8050108@dominion.kabel.utwente.nl>

> Michael Krelin schreef:
>>>> UNSHIPPED = "${libdir}/libpython2.4.so ${bindir}/smtpd.py"  #reason why
>>>> not package/ship it
>>>         Who exactly will go over all recipes and add such lines?
>> I take it the proposal was that package maintainers should take care of
>> it. Indeed, it would be better if intentionally unpackaged files invoked
>> no QA notice. But I think the solution is either not install them or rm
>> them after installation, depending on installation procedure nature.
> 
> Or we could patch package.bbclass[1] to do:
> 
> PACKAGES += "${PN}-leftovers"
> FILES_${PN}-leftovers = "/"

I'd rather propose, indeed, packaging the intentional leftovers into a
-leftovers package manually on each package that wants leftovers. But as
you pointed out that there are no valid reasons for files to be
unpackaged, I'm sure it's possible to come up with more meaningful name
for -leftovers package in each particular case. And before files are
packaged QA notice stays QA notice, because it *is* QA issue ;-)


Love,
H



  parent reply	other threads:[~2007-05-09 11:50 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
2007-05-09 11:51             ` Michael Krelin
2007-05-09 11:43       ` Michael Krelin [this message]
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=4641B3E4.1020107@klever.net \
    --to=hacker@klever.net \
    --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.