Thanks! Great questions! On Wed, Jan 29, 2014 at 03:25:18PM +0100, Tomas Forsman wrote: > I got some issues to understand the whole picture when it comes to F:20. > Will system-model still works as it does today?
Depends on *exactly* what you mean. Yes, system-model will still be the recommended way to use Conary to manage the system. f:20 per se won't have the rich group structure that fl:2 has. It will have a base set of imported packages and all the packages, but not the many groups. If fl:3 is based on f:20, then fl:3 could have a similarly rich group structure though probably it should be simplified, and definitely it should be implemented with GroupSetRecipe so that it cooks about 100 times faster... > Everything we install that's not in the "core" will show in system-model > and still easy to just remove the lines to get rid of it? Exactly. Once a system is "adopted", the system model says what should be there, and conary sync brings it into compliance with what is specified. > Also the updates, how will that actually work? Will we run, let's say every > third day to see if there is any updates in the "core" to fetch and how > will our system know about it? More like several times per day, so that security updates are quickly available through our repositories. After bringing in new packages, mirrorball will attempt to build new groups. If it fails, mails get send and we figure out the problem and fix it. Otherwise, the new group version automatically becomes available and "conary updateall" will find it. > Will we still have some lines in > system-model that say what version of F:20 we are running? You'll have a recognizable: search group-os=f20.flnx.org@f:20/20-1-1 search group-conary-packages=f20.flnx.org@f:20-c/20-1-1 install group-dist install group-conary-core install this that other install something=foresighters.rpath.org@f:20/12-1-1 Then after there's a security update, you run "conary updateall" and you get: search group-os=f20.flnx.org@f:20/20-2-1 search group-conary-packages=f20.flnx.org@f:20-c/20-1-1 install group-dist install group-conary-core install this that other install something=foresighters.rpath.org@f:20/12-1-1 And the security update is applied to your system. > Also wonders about gameway and foresighters repo, how will they look like > to easily to see what version of foresight they match? That's in my example above: to mark that packages should work against f:20, you create labels like what I have above. If a package is specifically only going to work against fl:3, even if fl:3 is built against f:20 (to start with), perhaps because it depends on some additional software added to fl:3 relative to f:20, then you would put it on the foresighters.rpath.org@fl:3 label instead. > Let's say we now got F:20, F:21 and F:22. Must be an easy way to tell users > how to install "minetest" in F:20 and F:22 in the repo address. like using: > gameway.rpath.org@fl:20 or something, im not sure if someone thinked > about that. Well, presumably you'll have a group of them, and as we move on to f:21 you might promote your group to gameway.rpath.org@f:21 and work from there; it will mark what you were building against. That part of the label is just informative to say the context in which things are expected to work; it isn't enforced. I still have packages I built on mkj.rpath.org@rpl:2 that work fine on fl2... > Feels more work to change whole repo address after every upgrade though, > but maybe it's better? Just ranting here.... There are specific reasons to do a new repository. One is that you can mirror only the F21 repository (someday) and not have to bring down all the F20 content too. And it doesn't matter very much what part of the "search" line you change to do an upgrade. > Will F:20 be installable in a easy way or do we also need to hack install > packages too, or will we get the same installation fedora has? My intention is that you install it by installing Fedora, and then running a single command of the "curl https://something | sh" variety that "adopts" the system and brings it under Conary management. If someone else wants to create mechanisms to install an already conary-managed F20, they are welcome to do the work. It just won't be me working on it. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
