public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: overseers@sources.redhat.com
Subject: Re: Tools for eCos 2.0
Date: Thu, 20 Feb 2003 01:43:00 -0000	[thread overview]
Message-ID: <20030220014329.GC11112@redhat.com> (raw)
In-Reply-To: <3E53EE9A.5060201@jifvik.org>

[Reply-To set to overseers]
On Wed, Feb 19, 2003 at 08:52:42PM +0000, Jonathan Larmour wrote:
>One of the things the eCos project needs for our upcoming release are
>prebuilt GNU tools for some of our primary targets. The burden of having
>to build tools, especially for windows users, can be quite large. Our
>users are embedded developers, not GNU enthusiasts per se!
>[snip]
>However eCos is big enough already (16Mb even in .tar.bz2 form!), and
>these tools will no doubt be popular - at least one tools download per
>eCos download.
>[snip]
>Anyway, I just wanted to run this by overseers to check for any comments. 
>Obviously if people think this is overkill and just allowing unrestricted 
>downloads would be fine, then we're not going to object :-).

Cygwin disallows direct downloads from sources.redhat.com, relying on
mirrors to handle this.  Without this restriction cygwin would probably
consume a significant portion of the bandwidth of sources.redhat.com.

I don't think there is any reason why eCos should be taking up a
disproportionate amount of bandwidth if, as you suspect, it will be
popular.  So we may decide to enforce the mirrors-only rule here.

I'm not sure that I understand the argument of users not being "GNU
enthusiasts".  Since you are targeting a technical audience, I don't see
why this is an issue.

I assume that you will be dealing with the GPL issues.  You will be
providing sources for all of the binaries you produce, right?  Are the
sources included in your disk space estimate?

On a more personal note, if you are going to be providing binaries that
duplicate anything that is already available in a cygwin release then I
would strongly object to that.

Finally, if you are using this in any way as a distribution method for a
commercial venture then I think it is not appropriate for
sources.redhat.com.

cgf

  reply	other threads:[~2003-02-20  1:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 20:52 Jonathan Larmour
2003-02-20  1:43 ` Christopher Faylor [this message]
2003-02-20 12:01   ` Jonathan Larmour

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=20030220014329.GC11112@redhat.com \
    --to=cgf@redhat.com \
    --cc=overseers@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).