From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] install optional symlinks from sendmail to ssmtp
Date: Sat, 30 Jun 2012 13:01:07 +0200 [thread overview]
Message-ID: <20120630110107.GV10551@pengutronix.de> (raw)
In-Reply-To: <7c5dc500779363ebdfeeb04cad5768ee@idefix.lespocky.dyndns.org>
Hi,
On Fri, Jun 29, 2012 at 11:19:22PM +0200, Alexander Dahl wrote:
> >> +ifdef PTXCONF_SSMTP_SENDMAIL
> >> + @$(call install_link, ssmtp, /sbin/ssmtp, /usr/sbin/sendmail)
> >> + @$(call install_link, ssmtp, ../sbin/sendmail, /usr/lib/sendmail)
> >> +endif
> > <snip>
> >
> > Why one time relative, the other time not? Plus, isn't ptxdists
> > install_link mechanism relative-only?
>
> I have to admit I didn't put too much thought in this and just copied
> what I found on my Debian system. I can't say anything about the link
> mechanism. I'll have a deeper look in this on Monday.
Nowadays PTXdist can handle relative and absolute links. We had relative
symlinks for a long time, because it made manipulating and checking the
nfsroot (platform-<plat>/root) easier. Now we have a 'ptxdist setup' option
to convert all absolute symlinks into relative symlinks in nfsroot only.
So just use what makes more sense. In this case I'd say, use absolute
symlinks.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-06-30 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 18:04 Alexander Dahl
2012-06-29 7:27 ` Josef Holzmayr
2012-06-29 21:19 ` Alexander Dahl
2012-06-30 11:01 ` Michael Olbrich [this message]
2012-07-02 7:56 ` Josef Holzmayr
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=20120630110107.GV10551@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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