From: Marc Kleine-Budde <mkl@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libcoap: add new package
Date: Wed, 05 Mar 2014 15:20:42 +0100 [thread overview]
Message-ID: <531732BA.6010404@pengutronix.de> (raw)
In-Reply-To: <20140305103724.GA2896@omega>
[-- Attachment #1.1: Type: text/plain, Size: 1176 bytes --]
On 03/05/2014 11:37 AM, Alexander Aring wrote:
> On Wed, Mar 05, 2014 at 10:48:54AM +0100, Michael Olbrich wrote:
>> Hi,
>>
>> On Wed, Mar 05, 2014 at 09:48:47AM +0100, Alexander Aring wrote:
>>> I see you applied other patch "libzmq: add new package" already. Is
>>> there something wrong with this patch or simple needs a little more time
>>> to review? :-)
>>
>> I need some clarification mostly. You're replacing the whole build-system.
>> That's not something I want to maintain inside ptxdist. I can only accept
>> that if this will be upstream the next time we update the package in
>> ptxdist. So what's the upstream status of these patches?
>>
> Maintainer don't want to use automake in his buildsystem, I think it
> will never go into mainline of libcoap. There is also no mailinglist for
> this project, I mailed with the maintainer private.
What about cmake?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-03-05 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:40 Alexander Aring
2014-03-05 8:48 ` Alexander Aring
2014-03-05 9:48 ` Michael Olbrich
2014-03-05 10:37 ` Alexander Aring
2014-03-05 14:20 ` Marc Kleine-Budde [this message]
2014-03-30 12:35 Alexander Aring
2014-04-01 14:11 ` Michael Olbrich
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=531732BA.6010404@pengutronix.de \
--to=mkl@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