Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pcsc-lite and ccid support
Date: Tue, 12 Jul 2011 09:17:30 +0200	[thread overview]
Message-ID: <20110712091730.6372c872@skate> (raw)
In-Reply-To: <CAG7bwA+MEJDb_1tXHQ82_R7_7eCmm1fwYnE2O0DSiMBwL0USqQ@mail.gmail.com>

Hello Dwi,

Le Tue, 12 Jul 2011 14:03:01 +0700,
Dwi Sasongko Supriyadi <ruckuus@gmail.com> a ?crit :

> > The latest ccid release is 1.4.4, dated May 2011, which doesn't
> > seem to be that old. In general, we prefer using stable releases
> > rather than SVN versions when possible. Do you have a good reason
> > for choosing a specific SVN version instead of the latest project
> > release ?
> >
> 
> It should have been using the latest version.
> 
> The reason is somehow fuzzy for me, and I need your advise. The idea
> is to keep the changes in .mk file as less as possible when there is
> new release, so in above case we only need to change the CCID_VERSION
> based on SVN version.
> 
> I agree to use the stable release which is in this case will look as
> follow:
> 
> CCID_VERSION = 1.4.4
> CCID_SOURCE = ccid-$(CCID_VERSION).tar.bz2
> CCID_SITE = https://alioth.debian.org/frs/download.php/3579
> 
> Comparing to the previous release: 1.4.3
> CCID_VERSION = 1.4.3
> CCID_SOURCE = ccid-$(CCID_VERSION).tar.bz2
> CCID_SITE = https://alioth.debian.org/frs/download.php/3535
> 
> There will be changes in CCID_VERSION and CCID_SITE when upgrading
> from 1.4.3 to 1.4.4
> 
> Please advise, should this is not reasonable

Well, I think updating two lines (CCID_VERSION and CCID_SITE) is
reasonable when the package version needs to be changed. It would of
course have been better if Alioth did not use this strange (and
stupid?) URL scheme, but that's the way it is.

> >> +CCID_AUTORECONF = YES

Presumably, if you use the tarball versions, the ./configure script and
Makefile.in files will already be available, so this line could be
removed.

> >> +##########################################################
> >> +#
> >> +# PCSC-Lite
> >> +#
> >> +# ########################################################
> >> +PCSC_LITE_VERSION = 5853
> >> +PCSC_LITE_SITE = svn://anonscm.debian.org/pcsclite/trunk/PCSC
> >
> > Same question, SVN version really needed ?
> >
> 
> Actually no. When checking out from SVN it will always get the latest
> version.

No, with what you have written, it will always get revision 5853, and
nothing else. It'd be better to use the tarball version here as well.

> >> +PCSC_LITE_AUTORECONF = YES

And remove this line.

> Many thanks for your comments. This is my first attempt on buildroot,
> I will try my best to accomplish it.

And your first attempt is very good! Thanks for contributing!

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-07-12  7:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12  6:28 [Buildroot] [PATCH] pcsc-lite and ccid support ruckuus at gmail.com
2011-07-12  6:43 ` Thomas Petazzoni
2011-07-12  7:03   ` Dwi Sasongko Supriyadi
2011-07-12  7:17     ` Thomas Petazzoni [this message]
2011-07-12 10:10       ` Dwi Sasongko Supriyadi
2011-07-12 11:50         ` Thomas Petazzoni
2011-07-12 15:07           ` Dwi Sasongko Supriyadi
  -- strict thread matches above, loose matches on Subject: below --
2011-07-12 10:10 ruckuus at gmail.com
2011-07-12 15:38 ` Thomas Petazzoni
2011-07-12 17:07   ` Dwi Sasongko Supriyadi
2011-07-13  7:38     ` Dwi Sasongko Supriyadi
2011-07-13  8:29       ` Thomas Petazzoni
2011-07-12 17:04 ruckuus at gmail.com

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=20110712091730.6372c872@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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