From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] package libfreefare: site url question
Date: Wed, 23 Oct 2013 21:58:18 +0200 [thread overview]
Message-ID: <52682A5A.1000708@mind.be> (raw)
In-Reply-To: <CACjG4BLNti1J9rH0Ks1jJnyGX=JztNJteMXp62x-zg43XHyeWw@mail.gmail.com>
On 18/10/13 13:23, arnaud aujon wrote:
> Hi,
>
> I noticed that libfreefare package refers to the site
> nfc-tools.googlecode.com <http://nfc-tools.googlecode.com>, even if the
> current archive (libfreefare-0.3.4) is present in nfc-tools repository,
> it seems better to use the libfreefare repository
> (libfreefare.googlecode.com <http://libfreefare.googlecode.com>).
> Is there a reason for that ?
Given that nobody has answered yet: I don't think there's a specific
reason for that. The two packages were added to buildroot at the same
time; maybe libfreerare didn't exist yet as a separate project.
You'll probably find other cases where the upstream site is no longer
accurate.
Regards,
Arnout
> As i'm working on a script to automatically check updates, it would be
> way easier for me :)
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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:[~2013-10-23 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 11:23 [Buildroot] package libfreefare: site url question arnaud aujon
2013-10-23 19:58 ` Arnout Vandecappelle [this message]
2013-10-23 20:26 ` arnaud aujon
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=52682A5A.1000708@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