Hi, > Today, the story suggests to use mirror2swift[2], but I'm afraid this > tool doesn't address the repodata creation, it only mirrors > the rpm packages when available (and it doesn't work with elasticsearch > http mirror where rpm files are not web listed).
Does it deserves an improvement of that tool then ? repodata should be browsable so I think the tool could fetch them ? Also could we add an option to specify directly the link to the RPMs in the config file and by exception not rely on the list ? That's just ideas I haven't look into the details. > Moreover we also discussed about using spacewalk[3] which seems a > complete solution to manage our ci instances need. My feeling is that we should let a SF operator setup and run by himself this kind of tool. I don't see s strong need to integrate that in SF. Furthermore I'm concern about the difficulty to integrate it tightly (in term of configuration). > Thus I wonder what to do now... From my understanding we need to rely on > yum utils to properly download a repository locally, and then use > createrepo to produces the required repodata. I'd like to finish the > original proposal and adds the missing swift publication code. So mirror2swift needs to be improve to handle that ? right ? Should we refine the story ? What's your feeling Christian ? Cheers, Fabien _______________________________________________ Softwarefactory-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/softwarefactory-dev
