From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Packaging questions
Date: Fri, 26 Jul 2013 09:43:01 -0600 [thread overview]
Message-ID: <51F29905.5040606@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0LbYYzeG0-kti7sj_cH7ji_b8xXJxYxSu6T=Snq++wJeUQ@mail.gmail.com>
On 2013-07-24 08:38, Burton, Ross wrote:
> On 24 July 2013 15:30, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> 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'm curious, what does the symlink point to? It's possible that we
>>> can refine the check to reduce the number of false positives, because
>>> this is a fairly common one that needs to be skipped.
>>
>>
>> The .so symlink points to a fully qualified library, e.g.
>> -rwxr-xr-x 1 gthomas gthomas 1383729 Jul 24 06:35 libamanda-3.3.3.so
>> lrwxrwxrwx 1 gthomas gthomas 18 Jul 24 06:35 libamanda.so ->
>> libamanda-3.3.3.so
>>
>> The problem seems to be that this is the unqualified .so name and not a
>> version qualified name like 'libamanda.so.3'. The package isn't building
>> the version qualified names, just the fully unqualified one.
>>
>>
>>>
>>> You can skip this QA test by setting INSANE_SKIP. In this case,
>>> INSANE_SKIP_${PN} = "dev-so" (you can identify the tag to use by
>>> looking through classes/insane.bbclass for the error message).
>
> So that's not the pattern that the test was designed for (not that
> it's actually implementing that design). I'm sure Amanda developers
> have a reason for this, but the presence of a .so symlink in a non-dev
> package is enough to trip this test, so INSANE_SKIP is the best thing
> to do.
One final packaging question. In my build I have these files:
/etc/amanda/
/etc/amanda/MyConfig/
/etc/amanda/MyConfig/tapelist
/etc/amanda/MyConfig/disklist
/etc/amanda/MyConfig/amanda.conf
I want the /etc/amanda/MyConfig to be packaged separately in "amanda-demo" package.
PACKAGES += " ${PN}-demo "
FILES_${PN}-demo += " \
/etc/amanda/MyConfig/ \
/amanda \
"
FILES_${PN} += "${libdir} \
${libexecdir}/amanda/* \
/var/amanda \
/etc/amanda \
"
Sadly, the /etc/amanda/MyConfig tree is ending up in the main package. How
can I stratify it the way I want?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-07-26 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 13:56 Packaging questions Gary Thomas
2013-07-24 14:12 ` Burton, Ross
2013-07-24 14:30 ` Gary Thomas
2013-07-24 14:38 ` Burton, Ross
2013-07-26 15:43 ` Gary Thomas [this message]
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=51F29905.5040606@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ross.burton@intel.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.