From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Add missing dependency to netatalk
Date: Mon, 05 Nov 2012 08:43:00 +0100 [thread overview]
Message-ID: <50976E04.4060009@mind.be> (raw)
In-Reply-To: <20121105075550.41dbed52@skate>
On 11/05/12 07:55, Thomas Petazzoni wrote:
> Dear Maxime Hadjinlian,
>
> On Sun, 4 Nov 2012 20:25:22 +0100, Maxime Hadjinlian wrote:
>
>> -NETATALK_DEPENDENCIES = openssl berkeleydb libgcrypt libgpg-error
>> +NETATALK_DEPENDENCIES = host-pkg-config openssl berkeleydb libgcrypt libgpg-error
>
> host-pkg-config should now be host-pkgconf.
>
> Peter, Arnout, shouldn't we be adding a dummy 'host-pkg-config' target
> in order to avoid breaking all external packages that are using
> host-pkg-config? Didn't we talk about not breaking APIs? :-)
Seems like a good idea.
But I would make it issue an error, so people update their .mk files.
Maybe we can create a top-level Makefile.legacy and Config.in.legacy that
collects all the API-compatibility-warnings-and-errors. That makes it easier
to remove them later.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-05 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 19:25 [Buildroot] [PATCH 1/2] Add missing dependency to netatalk Maxime Hadjinlian
2012-11-04 19:25 ` [Buildroot] [PATCH 2/2] Make BerkeleyDB optional for Netatalk Maxime Hadjinlian
2012-11-05 6:55 ` [Buildroot] [PATCH 1/2] Add missing dependency to netatalk Thomas Petazzoni
2012-11-05 7:43 ` Arnout Vandecappelle [this message]
2012-11-05 8:13 ` Peter Korsgaard
2012-11-05 8:14 ` Peter Korsgaard
2012-11-06 8:00 ` Maxime Hadjinlian
2012-11-08 21:31 ` [Buildroot] [PATCH 1/2] netatalk: " Maxime Hadjinlian
2012-11-08 21:32 ` Maxime Hadjinlian
2012-11-08 21:44 ` Maxime Hadjinlian
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=50976E04.4060009@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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