Re: gimp patch 1.1.32-1.2.0 [Also: Re: cmon guys, no patch from 1.1.32 to 1.2??]
Chris; On Wed, Jan 17, 2001 at 06:45:18PM -0500, Christopher W. Curtis wrote: [EMAIL PROTECTED] wrote: On 9 Jan, Christopher Curtis wrote: I don't see a public rsync server for gimp, cvs or otherwise. Perhaps this might be an acceptable option for people with modest bandwidth capabilities. There are anonymous CVS servers for the GIMP. Yes, yes there are. There are no *rsync* servers though, be they rsync'ing against a .tar, a .tgz, the CVS tree, or an extracted CVS tree. I'll set one up. I keep a fairly up-to-date mirror of anoncvs so I will add a cron job for that and put it up on my ADSL line. I'll get back to folks on this RSN. Cheers, Tom -- Tom Rathborne [EMAIL PROTECTED] http://www.aceldama.com/~tomr/ To be nobody-but-yourself -- in a world which is doing its best night and day, to make you everybody else -- means to fight the hardest battle which any human being can fight; and never stop fighting. -- e.e. cummings
Re: gimp patch 1.1.32-1.2.0 [Also: Re: cmon guys, no patch from 1.1.32 to 1.2??]
On 10 January, 2001 - Raphael Quinet sent me these 2.1K bytes:
Unfortunately, none of the three addresses mentioned for anoncvs
allowed me to get any files. One of them failed because of a server
configuration problem, another one could be reached but did not
respond, and the last one was apparently offline because it could not
be reached at all (no ping).
I admin anoncvs3.gnome.org (130.239.18.151) and it shouldn't have had
any problems, it's been _very_ stable for the last few years.
I hope that the situation is better for the non-anonymous CVS server.
I would be glad if anyone could give me the IP address of an anonymous
GNOME CVS mirror that works reasonably well for European users.
anoncvs3.gnome.org is in Sweden connected to the Swedish University
Network.
/Tomas
--
Tomas gren, [EMAIL PROTECTED], http://www.ing.umu.se/~stric/
|- Student at Computing Science, University of Ume
`- Sysadmin at {cs,ing,acc}.umu.se
Re: gimp patch 1.1.32-1.2.0 [Also: Re: cmon guys, no patch from 1.1.32 to 1.2??]
On 9 Jan, Christopher Curtis wrote: Patchsets also have a big problem which timecop already noticed: They don't contain binary files or patches to such and thus a patched tree might miss quite a few important files after a while. xdelta wouldn't cause that particular problem but is harder to use and deltas are not as obvious to read as an unified diff. I don't think that the majority of people applying patches really care what the format of the patch is (developers, of course, probably do, but not people like timecop or myself who prefer a xxxK patch to a xxMB download). They do; if we started now to switch over to deltas then quite a few people would complain about that. I definitely see the point, I'm behind a very narrow pipe as well so I prefer patches, too, but what is even more comfortable than patches is CVS, because they don't suffer from the problems patches do and are much easier to get and more complicated to mess up the source. I don't see a public rsync server for gimp, cvs or otherwise. Perhaps this might be an acceptable option for people with modest bandwidth capabilities. There are anonymous CVS servers for the GIMP. -- Servus, Daniel
Re: gimp patch 1.1.32-1.2.0 [Also: Re: cmon guys, no patch from 1.1.32 to 1.2??]
On Wed, 10 Jan 2001, [EMAIL PROTECTED] wrote: On 9 Jan, Christopher Curtis wrote: They do; if we started now to switch over to deltas then quite a few people would complain about that. I definitely see the point, I'm behind a very narrow pipe as well so I prefer patches, too, but what is even more comfortable than patches is CVS, because they don't suffer from the problems patches do and are much easier to get and more complicated to mess up the source. This is not true for everybody. For example, I usually access the Internet from work and I use a laptop, ZIP, CD-R or floppies to transfer files to my PC at home. A firewall prevents me from accessing anything that does not use FTP, HTTP or SMTP. This means that I can easily download patches and bring them home, but I cannot use CVS. Note that the absence of binary files in the patch files can also be considered as a feature for the weakly-connected users: the patches are much smaller because they do not contain the latest splash screen or brushes that is included in every new version. This saves half a megabyte for every download. I don't see a public rsync server for gimp, cvs or otherwise. Perhaps this might be an acceptable option for people with modest bandwidth capabilities. There are anonymous CVS servers for the GIMP. Two days ago, I installed a new modem on my home PC because I thought that after having spent several years working with semi-obsolete released versions of the source code, I should get the bleeding edge and use CVS from home (no firewall problems). So I tried to get the latest gimp from the anonymous CVS server(s). Unfortunately, none of the three addresses mentioned for anoncvs allowed me to get any files. One of them failed because of a server configuration problem, another one could be reached but did not respond, and the last one was apparently offline because it could not be reached at all (no ping). I hope that the situation is better for the non-anonymous CVS server. I would be glad if anyone could give me the IP address of an anonymous GNOME CVS mirror that works reasonably well for European users. -Raphael
Re: gimp patch 1.1.32-1.2.0 [Also: Re: cmon guys, no patch from 1.1.32 to 1.2??]
Raphael Quinet wrote:
Two days ago, I installed a new modem on my home PC because I thought
that after having spent several years working with semi-obsolete
released versions of the source code, I should get the bleeding edge
and use CVS from home (no firewall problems). So I tried to get the
latest gimp from the anonymous CVS server(s).
Unfortunately, none of the three addresses mentioned for anoncvs
allowed me to get any files.
snipped...
Reproduced from "Re: anonymous CVS is broken :(" thread, Jan-04-2001
Following courtesy of Tomas gren, striccommercial "at" signing.umu.se,
(who wrote...)
On 04 January, 2001 - Nix sent me these 0.5K bytes:
Whoever is providing anonymous CVS, it's broken.
Some of them are, not all.
Name:anoncvs.gnome.org
Addresses: 142.92.65.13, 192.58.206.110, 209.81.8.253, 130.239.18.151
Aliases: anoncvs.gimp.org
There are aliases anoncvs1.gnome.org - anoncvs4.gnome.org as well
1 and 3 (I admin #3) are working, 2 seems to not respond (routing
problems) and 4 has chmod problems. CC:ing the server admins.
As of this writing (Wed Jan 10 20:57:04 EST 2001) here's how the
pings go down from New York City
142.92.65.13PING anonvcs.gnome.org (142.92.65.13): 56 data bytes
64 bytes from 142.92.65.13: icmp_seq=0 ttl=241 time=240.624 ms
192.58.206.110 PING asterix.crl.dec.com (192.58.206.110): 56 data bytes
64 bytes from 192.58.206.110: icmp_seq=0 ttl=242 time=275.294 ms
209.81.8.253PING cvsonopn.varesearch.com (209.81.8.253): 56 data bytes
36 bytes from e2-1.community8-bi8000.valinux.com (198.186.202.94):
Destination Host Unreachable for icmp_seq=0
130.239.18.151 PING farbror.acc.umu.se (130.239.18.151): 56 data bytes
64 bytes from 130.239.18.151: icmp_seq=0 ttl=238 time=425.297 ms
Personally, CVS has made my life easier; no
need to sort out patch sets, and after the
working directory is in place, there are not
so vast amount of deltas that a refresh takes
any longer than 10-15 minutes (36K connection).
Plus, you can diff against earlier versions to
better track on-going code catastrophes ;).
Be good, be well
Garry
--
--
P.S. I'm starting the new century with a new ISP;
so my email address is changing:
gosgood "at" idt.net -- grosgood "at" rcn.com
Re: gimp patch 1.1.32-1.2.0 [Also: Re: cmon guys, no patch from 1.1.32 to 1.2??]
[EMAIL PROTECTED] wrote: Patchsets also have a big problem which timecop already noticed: They don't contain binary files or patches to such and thus a patched tree might miss quite a few important files after a while. xdelta wouldn't cause that particular problem but is harder to use and deltas are not as obvious to read as an unified diff. I don't think that the majority of people applying patches really care what the format of the patch is (developers, of course, probably do, but not people like timecop or myself who prefer a xxxK patch to a xxMB download). I don't see a public rsync server for gimp, cvs or otherwise. Perhaps this might be an acceptable option for people with modest bandwidth capabilities. (Just now catching up with holiday mail...) Chris
Re: gimp patch 1.1.32-1.2.0 [Also: Re: cmon guys, no patch from 1.1.32 to 1.2??]
On 26 Dec, Garry R. Osgood wrote: The tarballs and patch-sets are really meant for end-users who prefer to compile from source, but don't otherwise desire to get involved in maintenance and so don't have a strong motivation to keep a bleeding-edge source tree around. Patch sets are published with this laid-back attitude in mind, They lack the CVS administrative files which is a pity (but then, CVS admin directories don't always transplant themselves effortlessly. They depend on the context of particular users on particular clients using particular CVS servers) Patchsets also have a big problem which timecop already noticed: They don't contain binary files or patches to such and thus a patched tree might miss quite a few important files after a while. xdelta wouldn't cause that particular problem but is harder to use and deltas are not as obvious to read as an unified diff. I also noticed the first problem a while ago and thus I had to refetch the whole tarball every now and then which is a pain over a slow line. Luckily our maintainer is kind enough to provide bzipped tarballs while the GNOME maintainers in general haven't got the clue yet. -- Servus, Daniel
Re: gimp patch 1.1.32-1.2.0 [Also: Re: cmon guys, no patch from 1.1.32 to 1.2??]
[EMAIL PROTECTED] wrote: I got off my lazy arse and made a patch. I have no idea whether I did things correctly, I just downloaded the gimp- 1.1.32.tar.bz2 and gimp-1.2.0.tar.bz2 files, unpacked them, did diff -u -r gimp-1.1.32 gimp-1.2.0 gimp-patch, then bzip2'd that. It's 534kb, and you can download it from http://nova.student.utwente.nl/tc/gimp-patch-1.1.32- 1.2.0.bz2 Merry Christmas, Lourens Commendable, and in keeping with the spirit of the season. Thank you. Personally, I would strongly urge anyone desiring to support a Gnome or GNU/Linux project to learn about CVS. See http://cvsbook.redbean.com. The tarballs and patch-sets are really meant for end-users who prefer to compile from source, but don't otherwise desire to get involved in maintenance and so don't have a strong motivation to keep a bleeding-edge source tree around. Patch sets are published with this laid-back attitude in mind, They lack the CVS administrative files which is a pity (but then, CVS admin directories don't always transplant themselves effortlessly. They depend on the context of particular users on particular clients using particular CVS servers) After the initial working directory download (which can be painful on a slow, intermittent connection, but not prohibitive -- see below) keeping a working CVS directory current is painless, *especially* if one has a slow or intermittent connection. With CVS update, the server sends patches, not whole files, and per-patch compression somewhat lowers the absolute amount of bits to transfer (Steinar notes this could be better - agreed, but while the compressor could optimize across the entire patch set, it would not be as graceful in recovering if the connection dropped) Should a connection drop, the CVS client and server pickup can pick up where they left off -- check- pointing is an adjunct process to synchronizing a working tree with the repository. In contrast, not all ftp servers support restarting in an analogous way. And as for time, one can set up a cron job to do nightly syncs when one is asleep or otherwise occupied with something else, so it just happens that the tree is updated when you awake or come back to work. (with a little extra cleverness, the job can be written to restart dropped connections). Across the three or four projects I'm interested in, a weekly CVS hookup is generally complete in about fifteen to twenty minutes. (36K modem). Clearly, I could reduce the connect time if I synced nightly (fewer deltas). Apart from that, you have the CVS utilities available to access file update logs, find out who committed what, when and where, and other whatnot (Such information is also avalable from http://cvs.gnome.org/bonsai as well for many gnome projects). Most of all, you are liberated from wondering if a patch set matches a code base, since your CVS working directory and the repository it is associated with have per-file version granularity. See http://www.gimp.org/devel_cvs.html My two U. S. cents Garry
