Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] msmtp: add link to ${libdir}/sendmail
Date: Thu, 22 Nov 2012 10:25:29 +0800	[thread overview]
Message-ID: <50AD8D19.1090708@windriver.com> (raw)
In-Reply-To: <CAP9ODKpTfV_Lvi_0OhLrsGQxqSMwoqJjoR9yeCDkSkouV8ZqpA@mail.gmail.com>

On 2012年11月22日 04:57, Otavio Salvador wrote:
> On Wed, Nov 21, 2012 at 6:56 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org>  wrote:
>> On Wed, 2012-11-21 at 15:37 -0200, Otavio Salvador wrote:
>>> On Wed, Nov 21, 2012 at 3:34 PM, Richard Purdie
>>> <richard.purdie@linuxfoundation.org>  wrote:
>>>> On Wed, 2012-11-21 at 09:28 -0200, Otavio Salvador wrote:
>>>>> On Wed, Nov 21, 2012 at 7:38 AM, Kang Kai<kai.kang@windriver.com>  wrote:
>>>>>> LSB tests check file ${libdir}/sendmail, and the file was created by
>>>>>> package lsbsetup. Because lsbsetup is dropped, create the link in msmtp.
>>>>>>
>>>>>> Signed-off-by: Kang Kai<kai.kang@windriver.com>
>>>>> I think it is wrong. You should to use alternatives for it.
>>>> Not necessarily, its not a file conflict problem, it just needs to exist
>>>> at all...
>>> What if I want to use another smtp and still be lsb compliance?
>> The issue is we already have the "sendmail" bindir entry under update
>> alternatives control so this means adding an alternative of the
>> alternative which I think is getting convoluted. Ideally this symlink
>> just needs to exist which ever smtp is installed.
>>
>> So I think the better answer may be to move the link to the lsbtest
>> suite, or some kind of lsb-collateral package.

I will move the links to package lsb.

Thanks,
Kai


> This is a nicer solution indeed as this allow for reuse of same
> solution among other packages.
>




      reply	other threads:[~2012-11-22  2:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21  9:38 [PATCH 0/4] V2: drop lsbsetup Kang Kai
2012-11-21  9:38 ` [PATCH 1/4] lsbsetup: drop it Kang Kai
2012-11-21  9:38 ` [PATCH 2/4] packagegroup-core-lsb: remove lsbsetup Kang Kai
2012-11-21  9:38 ` [PATCH 3/4] chkconfig: add link files install_initd and remove_initd Kang Kai
2012-11-21  9:38 ` [PATCH 4/4] msmtp: add link to ${libdir}/sendmail Kang Kai
2012-11-21 11:28   ` Otavio Salvador
2012-11-21 17:34     ` Richard Purdie
2012-11-21 17:37       ` Otavio Salvador
2012-11-21 20:56         ` Richard Purdie
2012-11-21 20:57           ` Otavio Salvador
2012-11-22  2:25             ` Kang Kai [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=50AD8D19.1090708@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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