Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: coda - Coda distributed file system https://bugzilla.redhat.com/show_bug.cgi?id=446653 ------- Additional Comments From j.w.r.degoede@xxxxxx 2008-05-18 03:35 EST ------- (In reply to comment #5) > I have been working on some (experimental, private) packages for coda and > related libraries (since I work at CMU and share an office with the Coda lead > programmer). > > They are accessible at > /coda/coda.cs.cmu.edu/usr/agoode/devel/packaging > or > http://www.cs.cmu.edu/~agoode/coda-packaging/ > Hi, Nice to meet you and thanks for the interest in my coda packages > Some recommendations (as found in my packages): > * Splitting out /coda into another package. That way you avoid some disaster > when trying to upgrade coda-client during mounted /coda. I call this package > "coda-filesystem", which follows other Fedora conventions, but is a little odd > sounding. > I've already solved this by creating /coda if it doesn't exit in %post, and owning it through %ghost. This IMHO is better, because even a coda-filesystem package might need an update one day, and then you still have a problem. > * Use coda-client as the service name for the client, this is more intuitive > and follows how the Debian packages are. > This deviates from upstream, and makes it harder to use things like the coda howto and other documents together with the packages. > * Split out gcodacon Why? > * Ship a venus.conf that sets the coda directories to places in /var/log, > /var/run, etc I've moved the entire venus cache, logs etc to /var/lib/coda by adding a /usr/coda symlink which points to /var/lib/coda > Something needed but have not done yet: > * Add /etc/udev/makedev.d/99-coda.nodes with contents "cfs0" This is not necessary the venus initscript loads the coda kernel module and then the nodes get created automatically by udev p.s. As you may have seen I've written new sysv style initscript scripts for these packages which fully follow the Fedora / RH initscript conventions. I would like to share these with upstream, what would be the best place to submit these? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review