> > /usr/bin/ocropus sounds like it was installed from a package rather > > than from the sources. The ocropus command itself is pure C++ and > > doesn't use Python. > > It's /usr/bin/ocropus-pages and /usr/local/bin/ocropus for me. > Wouldn't it be more consistent to use only /usr or only /usr/local?
Well, the standard for manually installed software is to go into /usr/ local. The reason ocropus-pages ends up in /usr is because that's what Python's setup.py does by default. I don't think it would be a good idea to start installing the C++ commands into /usr/bin. On the other hand, I also don't think it's good to tinker with the setup.py paths because that probably breaks something. Overall, I think it's probably best to just live with the inconsistency for now (it doesn't seem to be causing any significant problems). Tom -- You received this message because you are subscribed to the Google Groups "ocropus" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/ocropus?hl=en.
