The foresight.rpath.org repository is getting unwieldy. The content store (of only unique files, compressed) is approaching 800GB. The database takes up over 100GB on disk. That alone would make it not particularly feasible to mirror from scratch, but it gets worse: the Foresight repository was one of the earliest Conary repositories, and so suffered from some early Conary bugs, and was even used for some Conary experiments, so it's actually impossible to mirror because Conary will give up. So the only way I can set up a mirror is to dump the database, copy the contents, restore the database onto the new location, and then mirror from there.
Putting FL3 into that repository seems like a really bad idea. I would like to propose that for FL3, we use a separate repository in the foresightlinux.org domain space. We'll use a label structure like I proposed back in September. I'd further propose that every time we change the major version of Foresight (not very often!) we create a new repository. Therefore, the repository name should probably include the version. So, something like f3.foresightlinux.org. Given that, putting the version number in the labels seems redundant. However, the version in the labels serves a different purpose: to indicate intended compatibility between repositories. That means that a label of f3.foresightlinux.org@fl:3-devel would not contain as much redundancy as it looks like. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
