All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Packaging questions
Date: Wed, 24 Jul 2013 07:56:25 -0600	[thread overview]
Message-ID: <51EFDD09.3030909@mlbassoc.com> (raw)

I'm [still] trying to set up a package for Amanda.  I'd like
the end result to match how it's done on other systems, e.g.
my desktop Fedora box.  However, this layout is causing some
QA errors which I don't know how to fix, e.g.

ERROR: QA Issue: non debug package contains .debug directory: amanda path 
/work/armv7a-vfp-neon-amltd-linux-gnueabi/amanda/3.3.3-r0/packages-split/amanda/usr/lib/perl/5.14.2/auto/Amanda/MainLoop/.debug/libMainLoop.so
ERROR: QA Issue: non -dev/-dbg/-nativesdk package contains symlink .so: amanda path 
'/work/armv7a-vfp-neon-amltd-linux-gnueabi/amanda/3.3.3-r0/packages-split/amanda/usr/lib/amanda/libamar.so'

I understand the first one but don't know the workaround.  How
do I tell bitbake that the directory /usr/lib/perl/5.14.2/auto/Amanda/MainLoop
contains executable code (and that's OK)?

The second issue I think is one of philosophy.  The symbolic link
is important to the package - how can I set this up to be OK?

Thanks for any pointers

Note: of course there are many of each of these classes of errors,
this is just a representative example.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2013-07-24 13:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 13:56 Gary Thomas [this message]
2013-07-24 14:12 ` Packaging questions Burton, Ross
2013-07-24 14:30   ` Gary Thomas
2013-07-24 14:38     ` Burton, Ross
2013-07-26 15:43       ` Gary Thomas
2013-07-26 15:52         ` Burton, Ross
2013-07-26 16:07           ` Gary Thomas

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=51EFDD09.3030909@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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.