Release online

Release online

[Jeffrey A Law]

Release is online & the release web pages are live (ie linked
in from the main egcs page).

ftp.cygnus.com:/pub/egcs/releases/egcs-1.0

bzip2 files aren't ready yet, but someone is working on them.

I'll be making the announcement shortly after I get some feedback
from a couple folks.

Thanks for your patience!

--


Jeff Law (law@cygnus.com)
Cygnus Solutions		EGCS GNU Compiler System
http://www.cygnus.com		http://www.cygnus.com/egcs

Re: Release online

[Myrdraal]

On Wed, Dec 03, 1997 at 11:35:52AM -0700, Jeffrey A Law wrote:
Hi,
 Any chance of your including a patch to 1201 to upgrade to 1.0? Downloading
 9.5mb takes a long time.
-Myrdraal

Re: Release online

[Jeffrey A Law]

  In message < 19971203172208.61518@jackalz >you write:
  > On Wed, Dec 03, 1997 at 11:35:52AM -0700, Jeffrey A Law wrote:
  > Hi,
  >  Any chance of your including a patch to 1201 to upgrade to 1.0?
  > Downloading 9.5mb takes a long time.
We certainly can if folks want it.

Note that the next snapshot will not be relative to the release,
but relative to the last snapshot, so if you were to apply the
diff to go from 1201 to egcs-1.0 you won't be able to then upgrade
to the next snapshot.

jeff

Re: Release online

[Joseph H. Buehler]

Myrdraal <myrdraal@jackalz.dyn.ml.org> writes:

>  Any chance of your including a patch to 1201 to upgrade to 1.0? Downloading
>  9.5mb takes a long time.
> -Myrdraal

I was using the patches until I had some problems because the modify
times get out of wack.  It would be nice to include in the patch a
file containing the mtime and file mode for everything in the source
tree...

Joe Buehler

Re: Release online

[H.J. Lu]

> 
>   In message < 19971203172208.61518@jackalz >you write:
>   > On Wed, Dec 03, 1997 at 11:35:52AM -0700, Jeffrey A Law wrote:
>   > Hi,
>   >  Any chance of your including a patch to 1201 to upgrade to 1.0?
>   > Downloading 9.5mb takes a long time.
> We certainly can if folks want it.

I'd like to see it. I only get a 28.8 modem link.

> 
> Note that the next snapshot will not be relative to the release,
> but relative to the last snapshot, so if you were to apply the
> diff to go from 1201 to egcs-1.0 you won't be able to then upgrade
> to the next snapshot.

It still beats a 9.5MB tar file.

-- 
H.J. Lu (hjl@gnu.org)

Re: Release online

[Jeffrey A Law]

  In message < m0xdfdR-0004ecC@ocean.lucon.org >you write:
  > > 
  > >   In message < 19971203172208.61518@jackalz >you write:
  > >   > On Wed, Dec 03, 1997 at 11:35:52AM -0700, Jeffrey A Law wrote:
  > >   > Hi,
  > >   >  Any chance of your including a patch to 1201 to upgrade to 1.0?
  > >   > Downloading 9.5mb takes a long time.
  > > We certainly can if folks want it.
  > 
  > I'd like to see it. I only get a 28.8 modem link.
Similarly for me at the moment :(

  > > Note that the next snapshot will not be relative to the release,
  > > but relative to the last snapshot, so if you were to apply the
  > > diff to go from 1201 to egcs-1.0 you won't be able to then upgrade
  > > to the next snapshot.
  > 
  > It still beats a 9.5MB tar file.
Right, but I suspect most (?) folks on this list will be upgrading
to the next snapshot.

I just want everyone to know that if we make the diff and they apply
it that they won't be able to then upgrade to the next snapshot.

It's also likely I'll just supply a single diff file for the ss1201 ->
egcs-1.0 changes -- they're small and making all those little diff files
is a pain when I can't use the standard snapshot process.

jeff

Re: Release online

[Jeffrey A Law]

  In message < m24t4pryq3.fsf@altera.gaithersburg.md.us >you write:
  > I was using the patches until I had some problems because the modify
  > times get out of wack.  It would be nice to include in the patch a
  > file containing the mtime and file mode for everything in the source
  > tree...
That's what the brik files are for -- they allow you to verify that the files
at your site match those in the snapshot.

jeff

Re: Release online

[Jeffrey A Law]

  In message < 199712042246.OAA22803@atrus.synopsys.com >you write:
  > > 
  > >   In message < m24t4pryq3.fsf@altera.gaithersburg.md.us >you write:
  > >   > I was using the patches until I had some problems because the modify
  > >   > times get out of wack.  It would be nice to include in the patch a
  > >   > file containing the mtime and file mode for everything in the source
  > >   > tree...
  > > That's what the brik files are for -- they allow you to verify that the f
  > iles
  > > at your site match those in the snapshot.
  > 
  > How about putting the brik program in pub/egcs/infrastructure?  A while
  > back, I requested this and put brik2.tar.gz into ftp.cygnus.com/incoming ..
  > don't know if it is still there.
I must have missed that message.  Agreed, it belongs in the infrastructure
directory.

Done.

jeff

Re: Release online

[Joe Buck]

> 
>   In message < m24t4pryq3.fsf@altera.gaithersburg.md.us >you write:
>   > I was using the patches until I had some problems because the modify
>   > times get out of wack.  It would be nice to include in the patch a
>   > file containing the mtime and file mode for everything in the source
>   > tree...
> That's what the brik files are for -- they allow you to verify that the files
> at your site match those in the snapshot.

How about putting the brik program in pub/egcs/infrastructure?  A while
back, I requested this and put brik2.tar.gz into ftp.cygnus.com/incoming ...
don't know if it is still there.

Re: Release online

[Oleg Krivosheev]

On Thu, 4 Dec 1997, Jeffrey A Law wrote:

>   In message < 199712042246.OAA22803@atrus.synopsys.com >you write:
>   > > 
>   > >   In message < m24t4pryq3.fsf@altera.gaithersburg.md.us >you write:
>   > >   > I was using the patches until I had some problems because the modify
>   > >   > times get out of wack.  It would be nice to include in the patch a
>   > >   > file containing the mtime and file mode for everything in the source
>   > >   > tree...
>   > > That's what the brik files are for -- they allow you to verify that the f
>   > iles
>   > > at your site match those in the snapshot.
>   > 
>   > How about putting the brik program in pub/egcs/infrastructure?  A while
>   > back, I requested this and put brik2.tar.gz into ftp.cygnus.com/incoming ..
>   > don't know if it is still there.
> I must have missed that message.  Agreed, it belongs in the infrastructure
> directory.
> 
> Done.
> 
> jeff

maybe brik Q&A in the FAQ ?

OK

Re: Release online

[Kamil Iskra]

On Thu, 4 Dec 1997, Jeffrey A Law wrote:

> I just want everyone to know that if we make the diff and they apply
> it that they won't be able to then upgrade to the next snapshot.

We can always make a backup copy of 1997-12-01 tree on our local machines,
apply the release patch to one copy and keep the backup for the next
snapshot...

/ Kamil Iskra - AMIGA 1200, 68030 50MHz, HDD 1.6 GB, 18 MB RAM \
| iskra@student.uci.agh.edu.pl  kiskra@ernie.icslab.agh.edu.pl |
| http://student.uci.agh.edu.pl/~iskra                         |
\ PGP public key available via Finger or WWW                   /

Re: Release online

[meissner]

| maybe brik Q&A in the FAQ ?

I would put md5sum (from textuitls-1.22) checksums in (either in addition to
the brik checksums or instead of).  The sum command is problematical, since the
AT&T and BSD camps had different sum commands.  I suspect we're the only people
in the world still using brik.