Filesystem tools and FUSE-related packages.
I'm wondering if it's worth creating a filesystems:ceph subproject, then moving ceph, ceph-deploy and any other ceph-only dependencies there, instead of in the base filesystems project?
- People who only want Ceph can use the filesystems:ceph repo, and can ignore the ~100 other non-ceph packages in filesystems.
- It seems somehow cleaner to me to have all the pieces of ceph, and possibly supporting packages in a separate subproject, rather than in the grab-bag of filesystems.
Comments? Complaints? A mailing list I should be taking this discussion to?
Makes sense to me, the number of ceph packages and support packages IMHO justify a separate project. The only "con" I could think of is a possible fragmentation of the devel projects, but I'd welcome to move the non-filesystem dependencies out of the base project.
I can't create the subproject myself but I'm giving it an ACK as one of the 'filesystems' maintainers.
I'm fine with that as well.
OK, I've created filesystems:ceph, and also filesystems:ceph:Unstable (the latter being where we can track bleeding edge upstream). I've granted maintenance rights to everyone who's a maintainer of filesystems who's ever accepted any requests against ceph or ceph-deploy. Hopefully I got the right bunch of people. If I missed anyone who wants to be up for ceph maintainership, please sing out.
Please submit delete requests for all relevant packages in filesystems after you finish the transition to :ceph.
Hi guys, seems the project should have openSUSE:XX.X:Update on it's build path to rebuild kernel-dependent packages in case kernel gets updated, eg.
<path project="openSUSE:13.2:Update" repository="standard"/>
<path project="openSUSE:13.2" repository="standard"/>
Not sure if this is enough, on my derived home project I have to add Required: kernel-obs-build to project config as well
Open Build Service (OBS) is an openSUSE project.