On Wed, Aug 21, 2013 at 06:03:50PM -0700, B Harder wrote: > Agreed. Hyphens in libnames don't look pleasing to my eye (fwiw), > libfossilscm (cc ... -lfossilscm ...) might be next best to > disambiguate from potential collision w/ another libfossil, though it > too is pretty ugly looking. > > Brief search yields https://github.com/paulfitz/libfossil as second > hit (after this very discussion). I also searched for libfsl, which > appears to be claimed, I didn't look into what that project is.
As it happens, that GitHub hit appears to be someone's work on a library for Fossil SCM. Glancing across some of the code, it looks like it's a Ruby libfossil, so there'd be no practical namespace clash -- only a search engine namespace clash, which is a common case for libraries that do the same things in different languages anyway. I don't think that's much of an impediment. It currently has six commits, all from July, according to GitHub. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
