r7908 - in trunk/BOOK: . gnome/core introduction/welcome
wblaszcz at bigpond.net.au
Thu Jul 30 06:58:18 PDT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Randy McMurchy wrote:
> How do you determine what versions of the different packages make up
> a Core GNOME release? Just FYI, I've always done it like this:
> First go to http://ftp.gnome.org/pub/gnome/platform/2.26/2.26.3/sources/
> and see what is listed. Then go to the actual source directory for a
> particular package and see if there is an updated version. If there is,
> I'd look at NEWS and the ChangeLog to see if it fixed a bug that was
> in the release version. I've been known to use an updated version if
> I felt it fixed a bug, or made it better.
> Just curious how you are going to go about it.
I do the first part, go to
I don't do the second part, go the actual source directory for a
particular package. I figured that later versions would be deemed for a
later version of GNOME, e.g. 2.26.4.
> Just so you know, I had those lines offset on purpose. This shows the reader
> that it is a continued line and not a new --variable. Just FYI, but I had
> done that on purpose.
> The same as if you have a sed command, we do it like this:
> sed -i -e "kdjfkasjdlkfjdkjfla;ksdjflkadsjfkdsjal;fjdsakfj" \
Sorry about this. I did some reformatting on these pages several months
ago, and at the time I thought I was aligning it up nicely at the time
(I can't remember how) but obviously it didn't work. I'll fix it up
tomorrow. Oh that's right, it's when I had CONFIGPARMS all over the place.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the blfs-book