@m.shulhan @hervinhioslash Thanks for the suggestion. I agree that using a runtime mechanism like env vars or command line flag can solve this problem. But the path value is for internal use, it should be customized only by the system administrators or package managers who determine where to install things, but not by the users of the package. If the referenced file lives at /usr/lib/name/file, it makes no sense to ask users to point to another location.
So am I correct to assume that there currently exists no convention to specify a const path like this? Maybe I should just write a configure script that generate a go file containing the const paths? Is providing a configure script in a go project something frowned upon? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/FA2CAE6D-C96D-4FCF-9F89-C7021A02B854%40gmail.com.
