All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:07:37 -0600	[thread overview]
Message-ID: <51F29EC9.7060400@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0LaBhvu9+hJtU7fdO58d+sTAjsfW3VxBJ1Ke+oJ-cNtDkA@mail.gmail.com>

On 2013-07-26 09:52, Burton, Ross wrote:
> On 26 July 2013 16:43, Gary Thomas <gary@mlbassoc.com> wrote:
>> 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?
>
> Various things interacting explain this.  Package takes files in the
> order that they appear in PACKAGES, so by using += you're *appending*
> amanda-demo to PACKAGES, so it's at the end.  FILES_$PN defaults to a
> long list of "useful" paths, including ${sysconfdir}.
>
> So, two options, both of which will work:
>
> 1) prepend amanda-demo to PACKAGES, so it gets to take files first. =+
> is the prepend operator.
> 2) Change FILES_$PN to explictly set the entire value instead of
> appending the default, then you can leave out $sysconfdir.

Option #1 is perfect and does just what I want, thanks!

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


      reply	other threads:[~2013-07-26 16:07 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
2013-07-26 15:52         ` Burton, Ross
2013-07-26 16:07           ` Gary Thomas [this message]

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=51F29EC9.7060400@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.