From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] ibrdtn: add packaging rules for IBR-DTN and dtndht
Date: Thu, 8 Sep 2016 08:35:12 +0200 [thread overview]
Message-ID: <20160908063512.n6n66zox7evcfzvp@pengutronix.de> (raw)
In-Reply-To: <1e002e8f-084b-077a-0504-872415525ce0@rohieb.name>
On Thu, Sep 08, 2016 at 03:07:27AM +0200, Roland Hieber wrote:
> On 07.09.2016 15:48, Michael Olbrich wrote:
> >> +menuconfig IBRDTND
> >> + tristate
> >> + prompt "ibrdtnd "
> >> + select IBRDTN
> >> + select LIBC_M
> >> + select LIBDAEMON if IBRDTND_ENABLE_DAEMON
> >> + select DTNDHT if IBRDTND_ENABLE_DTNDHT
> >> + select IBRCOMMON_WITH_OPENSSL if IBRDTND_WITH_TLS
> >
> > This looks wrong. If IBRCOMMON is needed then you must select the toplevel
> > symbol as well.
>
> Right, thanks. IBRCOMMON is already selected indirectly by selecting
> IBRDTN, but I have now also added it here for clarification.
>
> >> +# ----------------------------------------------------------------------------
> >> +# Target-Install
> >> +# ----------------------------------------------------------------------------
> >> +
> >> +$(STATEDIR)/ibrdtnd.targetinstall:
> >> + @$(call targetinfo)
> >> +
> >> + @$(call install_init, ibrdtnd)
> >> + @$(call install_fixup, ibrdtnd,PRIORITY,optional)
> >> + @$(call install_fixup, ibrdtnd,SECTION,base)
> >> + @$(call install_fixup, ibrdtnd,AUTHOR,"Roland Hieber <rohieb@rohieb.name>")
> >> + @$(call install_fixup, ibrdtnd,DESCRIPTION,missing)
> >> +
> >> + @$(call install_copy, ibrdtnd, 0, 0, 0755, -, /usr/sbin/dtnd)
> >> + @$(call install_alternative, ibrdtnd, 0, 0, 0644, /etc/ibrdtnd.conf)
> >> +
> >> +ifdef PTXCONF_IBRDTND_WITH_TLS
> >> + @$(call install_copy, ibrdtnd, 0, 0, 0755, -, /usr/bin/ibrdtn-genkey.sh)
> >> + @mkdir -p ${ROOTDIR}/etc/ibrdtn/bpsec ${ROOTDIR}/etc/ibrdtn/certs
> >
> > No, you nned to do this to create a directory:
> >
> > @$(call install_copy, ibrdtnd, 0, 0, 0755, /etc/ibrdtn/certs)
> >
> > Michael
>
> Yes right, this was already noted by Robert Schwebel, I have already
> edited it in my local working copy, and will send an updated patch once
> the key generation in /etc/rc.once is working. But unfortunately there
> are currently things of higher priorities for me, so this will probably
> still take a while :-/
I know the feeling. I have a lot of 'not quite ready for mainline' patches
lying around for various other projects. And a few for ptxdist as well...
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
prev parent reply other threads:[~2016-09-08 6:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 14:53 [ptxdist] [PATCH] " Roland Hieber
2016-08-18 6:53 ` Michael Olbrich
2016-08-23 4:41 ` Roland Hieber
2016-08-25 11:02 ` Michael Olbrich
2016-08-25 15:11 ` Robert Schwebel
2016-08-28 5:27 ` Roland Hieber
2016-08-28 7:36 ` Robert Schwebel
2016-08-28 18:36 ` Roland Hieber
2016-09-01 9:58 ` Michael Olbrich
2016-09-01 15:09 ` Alexander Dahl
2016-08-29 7:42 ` Juergen Borleis
2016-08-18 10:15 ` Michael Olbrich
2016-08-28 5:32 ` [ptxdist] [PATCH v2] " Roland Hieber
2016-09-07 13:48 ` Michael Olbrich
2016-09-08 1:07 ` Roland Hieber
2016-09-08 6:35 ` Michael Olbrich [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=20160908063512.n6n66zox7evcfzvp@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