From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] downloads: add basic CVS support
Date: Wed, 04 Sep 2013 13:41:44 -0300 [thread overview]
Message-ID: <522762C8.5090104@zacarias.com.ar> (raw)
In-Reply-To: <20130904182446.22d09a4a@skate>
On 09/04/2013 01:24 PM, Thomas Petazzoni wrote:
>> The support is for pserver mode anonymous CVS.
>> source-check is based on login since many servers don't support or have
>> ls/rls disabled.
>>
>> Usage is pretty straightforward.
>> PKG_SITE defines the site hostname and remote directory.
>> The module is defined by the bare package name.
>> Version is date based.
>
> Those details should probably go into an update of
> docs/manual/adding-packages-generic.txt, which documents all the source
> methods.
Yes, that'll follow once the method is accepted as proposed, docs aren't
easy to modify if there's substantial change.
> Not related to your change, but interesting to see that LOCALFILES is a
> SCM :)
Well, if someone wants RCS that might be syntactically correct, not for
now though ;)
> Maybe we could replace this with SOURCE_CHECK_*
> and similar here :-)
Sure, i can follow up with the docs patchset.
> This line is quite long. Split it maybe?
True, DOWNLOAD_GIT also exceeds the 80 column "standard", and so do
other parts so don't blame me :)
I also do on SOURCE_CHECK_CVS but that's hardly splittable in a
coherent/useful way, and cvs is very picky with parameter order to
rephrase it.
Regards.
prev parent reply other threads:[~2013-09-04 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 15:53 [Buildroot] [PATCH 1/2] downloads: add basic CVS support Gustavo Zacarias
2013-09-04 15:53 ` [Buildroot] [PATCH 2/2] elf2flt: upgrade to latest version Gustavo Zacarias
2013-09-12 22:32 ` Peter Korsgaard
2013-09-04 16:24 ` [Buildroot] [PATCH 1/2] downloads: add basic CVS support Thomas Petazzoni
2013-09-04 16:41 ` Gustavo Zacarias [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=522762C8.5090104@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.