From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device
Date: Mon, 17 Sep 2007 11:27:35 +0200 [thread overview]
Message-ID: <20070917092735.GA18888@aon.at> (raw)
In-Reply-To: <1190025802.8052.4.camel@elrond.sweden.atmel.com>
On Mon, Sep 17, 2007 at 12:43:22PM +0200, Ulf Samuelsson wrote:
>m?n 2007-09-17 klockan 00:55 -0700 skrev aldot at uclibc.org:
>> Author: aldot
>> Date: 2007-09-17 00:54:52 -0700 (Mon, 17 Sep 2007)
>> New Revision: 19862
>>
>> Log:
>> - Atmel mirrors are only of interrest for atmel
>>
>>
>> Modified:
>> trunk/buildroot/target/device/Mirrors.in
>>
>>
>
>And making it depending on BR2_ATMEL or similar makes it impossible to
>put package support on that ftp site, so don't create any dependency
>at all.
This can depend on BR2_TARGET_ATMEL or some at91 config symbol.
Depending on BR2_arm is wrong since i want to build arm toolchains but
use upstream sources, not some vendor supplied tarballs.
If we need to mirror certain packages, we can of course do this (as the
buildroot project), but using random vendor's locked-down ftp server for
this purpose is not a sensible thing to do, IMO.
next prev parent reply other threads:[~2007-09-17 9:27 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 7:55 [Buildroot] svn commit: trunk/buildroot/target/device aldot at uclibc.org
2007-09-17 8:03 ` Hans-Christian Egtvedt
2007-09-17 8:38 ` Bernhard Fischer
2007-09-17 10:41 ` Ulf Samuelsson
2007-09-17 10:43 ` Ulf Samuelsson
2007-09-17 9:27 ` Bernhard Fischer [this message]
2007-09-17 12:16 ` Ulf Samuelsson
2007-09-17 11:10 ` Bernhard Fischer
2007-09-17 14:56 ` Ulf Samuelsson
2007-09-17 13:41 ` Bernhard Fischer
2007-09-18 6:54 ` Ulf Samuelsson
2007-09-19 8:21 ` [Buildroot] local mirror management (bug #572) Bernhard Fischer
2007-09-19 21:53 ` Ulf Samuelsson
2007-09-19 21:20 ` Bernhard Fischer
2007-09-20 6:40 ` Ulf Samuelsson
2007-09-20 21:38 ` Elizabeth Oldham
2007-09-21 7:44 ` Bernhard Fischer
-- strict thread matches above, loose matches on Subject: below --
2009-01-29 17:28 [Buildroot] svn commit: trunk/buildroot/target/device ulf at uclibc.org
2009-01-29 17:26 ulf at uclibc.org
2009-01-29 17:23 ulf at uclibc.org
2009-01-29 17:22 ulf at uclibc.org
2009-01-29 17:22 ulf at uclibc.org
2009-01-29 17:21 ulf at uclibc.org
2009-01-29 19:04 ` Peter Korsgaard
2009-01-29 22:06 ` Ulf Samuelsson
2008-11-14 10:06 jacmet at uclibc.org
2008-11-14 10:12 ` Thomas Petazzoni
2008-11-14 11:15 ` Peter Korsgaard
2008-07-05 21:57 ulf at uclibc.org
2008-07-05 6:37 ulf at uclibc.org
2008-07-05 6:47 ` Thiago A. Corrêa
2008-07-05 11:42 ` Ulf Samuelsson
2008-07-07 6:09 ` Hans-Christian Egtvedt
2008-07-03 8:29 ulf at uclibc.org
2008-03-19 7:26 ulf at uclibc.org
2007-12-17 13:14 vanokuten at uclibc.org
2007-09-29 20:47 ulf at uclibc.org
2007-09-29 19:46 aldot at uclibc.org
2007-09-25 22:04 aldot at uclibc.org
2007-09-25 22:39 ` Ulf Samuelsson
2007-09-25 21:40 aldot at uclibc.org
2007-09-17 9:26 ulf at uclibc.org
2007-08-19 18:26 ulf at uclibc.org
2007-08-01 9:06 ulf at uclibc.org
2007-07-31 22:57 ulf at uclibc.org
2007-07-31 15:39 aldot at uclibc.org
2007-07-31 15:37 aldot at uclibc.org
2007-03-18 11:53 aldot at uclibc.org
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=20070917092735.GA18888@aon.at \
--to=rep.dot.nop@gmail.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