From: Chong Lu <Chong.Lu@windriver.com>
To: Paul Barker <paul@paulbarker.me.uk>,
<openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 1/3] vim: add dependency and selinux and acl support control
Date: Tue, 6 May 2014 10:55:22 +0800 [thread overview]
Message-ID: <53684F1A.7000100@windriver.com> (raw)
In-Reply-To: <20140505214541.GB12987@gmail.com>
On 05/06/2014 05:45 AM, Paul Barker wrote:
> On Fri, Apr 18, 2014 at 06:16:30PM +0800, Chong Lu wrote:
>> FILES_${PN}-data = "${datadir}/${PN}"
>> +FILES_${PN}-common = " \
>> + ${datadir}/${PN}/${VIMDIR}/*.vim \
>> + ${datadir}/${PN}/${VIMDIR}/autoload \
>> + ${datadir}/${PN}/${VIMDIR}/colors \
>> + ${datadir}/${PN}/${VIMDIR}/compiler \
>> + ${datadir}/${PN}/${VIMDIR}/ftplugin \
>> + ${datadir}/${PN}/${VIMDIR}/indent \
>> + ${datadir}/${PN}/${VIMDIR}/keymap \
>> + ${datadir}/${PN}/${VIMDIR}/lang \
>> + ${datadir}/${PN}/${VIMDIR}/macros \
>> + ${datadir}/${PN}/${VIMDIR}/plugin \
>> + ${datadir}/${PN}/${VIMDIR}/print \
>> + ${datadir}/${PN}/${VIMDIR}/spell \
>> + ${datadir}/${PN}/${VIMDIR}/tools \
>> +"
>>
>> # Recommend that runtime data is installed along with vim
>> RRECOMMENDS_${PN} = "${PN}-syntax ${PN}-help ${PN}-tutor ${PN}-vimrc ${PN}-data"
> Sorry to reply to an old commit but this has broke things for me. Installing vim
> after this commit gives:
>
> vim: unsatisfied recommendation for vim-data
>
> As everything that was in vim-data is now in vim-common. Your commit message
> says "Split binary file into vim package and put others in vim-common.", but
> this split was already in effect with everything in vim-data. It then got
> installed by default as vim-data is in RRECOMMENDS_vim, but could be disabled by
> adding things to BAD_RECOMMENDS.
>
> What is the benefit of moving things to vim-common? I'm probably just
> misunderstanding what this change is aiming to solve.
I just refer to Ubuntu splitting package policy.***
<https://bbs.archlinux.org/viewtopic.php?id=173515>*
>
> As vim-data is now left empty, can we remove it from PACKAGES and
> RRECOMMENDS_vim and instead add vim-common to RRECOMMENDS_vim? Just want to make
> sure that won't break anything for you before I send a patch.
Sorry for my mistake. we should remove vim-data from PACKAGES and
RRECOMMENDS_vim and
add vim-common to RRECOMMENDS_vim.
> Thanks,
>
next prev parent reply other threads:[~2014-05-06 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 10:16 [PATCH 0/3] vim: add dependency and selinux and acl support control Chong Lu
2014-04-18 10:16 ` [PATCH 1/3] " Chong Lu
2014-04-21 11:32 ` Martin Jansa
2014-05-05 21:45 ` Paul Barker
2014-05-06 2:55 ` Chong Lu [this message]
2014-05-06 10:01 ` Paul Barker
2014-05-06 5:08 ` Chong Lu
2014-04-18 10:16 ` [PATCH 2/3] vim: don't check acl header if acl support disabled Chong Lu
2014-04-18 10:16 ` [PATCH 3/3] vim: add knob whether elf.h are checked Chong Lu
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=53684F1A.7000100@windriver.com \
--to=chong.lu@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox