In message: <200305281524.10145.doconnor_at_gsoft.com.au> "Daniel O'Connor" <doconnor_at_gsoft.com.au> writes: : You need 'FORCE_PKG_REGISTER=' in the install target. True. : 1) If the port is updated between builds you end up with two version of the : port installed. True. That's a weakness in the ports system, which is why we have portupgrade. However, I didn't want to require portupgrade for something so 'simple'. : 2) You can't control where the module gets put - arguably this isn't a : calamity, but I think it makes more sense for the modules to end up in : /boot/modules, or some analog to it that is in $PREFIX. It should go in /boot/kernel, and not into $PREFIX, but that's a philisophical problem I have with ports. ALL modules should be in /, imho, since you don't know if the module is required to mount /. : I guess the problem with mandating somewhere in $PREFIX is that the loader : can't load it, so that's no good. I guess the only choice left is : /boot/modules. /boot/kernel : Any comments? Well, the patch was mostly a strawman to promote discussions about the issues. WarnerReceived on Wed May 28 2003 - 00:14:29 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:09 UTC