Thanks. I do understand how packages work; it was just that I have not run into a thing like weewx that has a functioning build/install system, but where one isn't supposed to use it when building a package. In all the rest of the things I've dealt with (probably over 100), the package config files do "configure/make" at build time (or equivalent), and then "make install" into a destdir, and then tar that up. I have now been enlightened that weewx's approach is to have packagers hand-write a bunch of install statments in the packaging config files instead, and that "setup.py install" is set up for non-package installs with a different layout (that fits for easy removal, into a distinct prefix). I see the rationale - it's just something new to me.
Interesting about debian and pre-answered questions; that seems very helpful when you are scripting things and have already debugged how you want it. It's easy enough to document that the user should run wee_config, so I'm not going to worry about facilities like that. I also understand now the non-packaged extension approach. Some packaging systems (including pkgsrc) have a notion that files shouldn't get written in the package-system-controlled prefix, other than by the package manager. But I realize that's far from universal and don't mean to rail against it - at this point I am just trying to understand, and I think I do ow. -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/rmi5znbchle.fsf%40s1.lexort.com.
