Hello All,
I know that a question similar to this has been asked on this list, but i want to be sure that i understand it correctly.
If i install FC2-test1 on my box and i point my yum to the development tree:
[development] name=Fedora Core $releasever - Development Tree baseurl=ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/$basearch
and i upgrade all packages from the development tree it is enough to have FC2-test2 installed or i should download the FC2-test2 to have the all new packages?
Or simply, it is enough if i update my release always from the development tree to have the latest release/test release installed on my box? or i should download the released isos every time and then upgrade to the development tree to have the latest and newest packages?
Thanks a lot, Julius
On Wed, 2004-03-31 at 20:38, P.I.Julius wrote:
Or simply, it is enough if i update my release always from the development tree to have the latest release/test release installed on my box? or i should download the released isos every time and then upgrade to the development tree to have the latest and newest packages?
That's basically what I did on a box last week (I needed to re-install but FC2T1 was the 'current' release), so I installed from the FC2T1 media then did a complete update (it was a little sticky, because of major changes like XFree86 to xorg and Evo 1.5 dropping to Evo 1.4), then, once FC2T2 was released, I did an upgrade from the media.
Some things, like SELinux, are missing, but the system is stable. It's certainly not a production server or anything, just a sort of sandbox. I don't consider it stable (in a "changed-ness" sense) enough to report bugs against unless I get independent corroboration from a cleanly installed FC2T2 box.
In short, it works, but I don't think it's recommended (or possibly even sane). :-)
Ben
P.I.Julius said:
Or simply, it is enough if i update my release always from the development tree to have the latest release/test release installed on my box?
It is not preferred for the same reason doing an Anaconda update from test1 -> test2 isn't preferred:
a) Packages can be reverted to earlier versions (for example Evolution) b) Any _new_ packages won't be installed, so you aren't doing a test of what the final code will be (for example SELinux, which is a major focus of test2). c) Any "left over" files/packages can cause issues and are a pain to track town (for example the error in one of the XFree86 scripts causing the ldconfig to not be updated).