On 14.10.2008 18:19, Mike Chambers wrote:
On Tue, 2008-10-14 at 17:53 +0200, Thorsten Leemhuis wrote:
As you'll likely have heard by now: RPM Fusion ( http://rpmfusion.org ),
the merger of Dribble, Freshrpms and Livna gets closer to its official
release/start. Most of the packages from Livna have been imported and
build for RPM Fusion already, hence we now begin to slowly move users
from Livna over to RPM Fusion by activating the RPM Fusion free and
nonfree rawhide repos for users of livna's devel branch *now*.
Why the repo, updates.repo and updates-testing.repo, and rawhide-repo?
Note that Livna not only had "one repo" -- it also had a testing and
rawhide repo. So it's just one more then before in fact.
I guess what I am asking, is why not just the repo itself (which would
have all the updates as well), testing I guess for the updates are
official, and then the devel/rawhide repo?
Your kind of gonna do same thing as Fedora, such as a base, then
updates, testing, and a rawhide version?
Exactly. Two of the reasons for it:
- Spins
- using RPM Fusion directly during Fedora install
Both is not easily possible to support with the "one main add-on repo
without a updates-repo" approach livna had, as then packages from livna
sometimes require updated Fedora packages -- thus it worked in the
installer or during spin creation only if you enabled the Fedora updates
repo as well. Now you don't need to do that (but you of course can, as
long as you enable the update repos from both Fedora and RPM Fusion)
CU
knurd
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
