All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Junqian Gordon Xu <xjqian@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: QA for intentionally unpackaged files
Date: Wed, 9 May 2007 12:38:21 +0300	[thread overview]
Message-ID: <02827798.20070509123821@gmail.com> (raw)
In-Reply-To: <464130FC.7030008@gmail.com>

Hello Junqian,

Wednesday, May 9, 2007, 5:25:00 AM, you wrote:

> Now there is no way to distinguish if the following is intensional by 
> the package maintainer or an oversight without taking a closer look at
> the contents

        So, maybe "closer look" is indeed a solution here?

> NOTE: the following files were installed but not shipped in any package:
> NOTE:   /usr/lib/libpython2.4.so
> NOTE:   /usr/lib/.debug/libpython2.4.so.1.0
> NOTE:   /usr/share/man/man1/python.1
> NOTE:   /usr/bin/python2.4
> NOTE:   /usr/bin/smtpd.py
> NOTE:   /usr/bin/.debug/python

> Maybe we should have something in insane.bb to take care of the 
> intentionally unpackaged crusts. So we can do something like the 
> following in a bb file to intensionally leave out some garbage unpackaged:

> 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?

> so during do_package or package_QA, it would show as

> NOTE: the following files were installed but not shipped in any package:
> NOTE:   /usr/lib/libpython2.4.so   UNSHIPPED #reason why not 
> packaged/ship it

        No, thanks, it likely shouldn't dump them at all then.

> NOTE:   /usr/lib/.debug/libpython2.4.so.1.0
> NOTE:   /usr/share/man/man1/python.1
> NOTE:   /usr/bin/python2.4
> NOTE:   /usr/bin/smtpd.py  UNSHIPPED #reason why not packaged/ship it
> NOTE:   /usr/bin/.debug/python

> Is SUNK a better word than UNSHIPPED?

        No.

> Gordon


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




  reply	other threads:[~2007-05-09  9:38 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 [this message]
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
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=02827798.20070509123821@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=xjqian@gmail.com \
    /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.