On Sun, Jul 16, 2006 at 10:07:52PM +0200, Mark Rosenstand wrote:
It's impossible for now, as we have one reject directory for all packages. This would possible if we introduce /var/lib/pkg/rejected/packageA/, /var/lib/pkg/rejected/packageB/, ...
But I don't really like that idea.
I suspect that this is an issue in theory only. pkgadd already warns when rejecting files, meaning the user should run rejmerge ASAP. It's possible (but unlikely) that the same directory will get rejected from different packages, but the overwrite in /var/lib/pkg/rejected don't really cause any trouble. (Hey, this is how it works now, except the stuff is merged directly to our filesystems without any warnings!)
Ok. Another issue with rejecting: accidentally package have /usr/share/ owned by someone else, but not root. /usr, /usr/bin, /usr/etc are fine. Half of the package installed and half is rejected. What user suppose to do?
prtdir +! /usr/ports/core prtdir ! /usr/ports/opt prtdir /usr/ports/contrib
+ is "I trust you to run post-install" ! is "I trust you to pass -i option"
This seems overly complicated and cryptic to me. I think we'd be better off changing the config file format completely, like:
[core] directory /usr/ports/core run-scripts yes
[contrib] directory /usr/ports/contrib run-scripts no
Since it scales so much better (when we want feature Z, we won't have to add yet another weird, non-logical character.)
Yep, looks much friendly. -- Anton (irc: bd2)