Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: kismet -- A WLAN detector, sniffer and IDS https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=165314 ------- Additional Comments From jkeating@xxxxxxxxxx 2006-04-25 16:25 EST ------- (In reply to comment #21) > (In reply to comment #20) > > ... are required resp. the best current way to express: > > > > * the directory must exist before the package places files into it. Else, > > when the directory is a symlink (e.g. compare /etc/init.d) in the owning > > package, you will create oddities. > > > > * the package must be removed before the directory. Else, the directory > > can not be removed because it still contains files from 'kismet' and > > becomes orphaned. Therefore, a strict '%crontabdir -> kismet' order > > on installation, and 'kismet -> %crontabdir' order on uninstallation > > is required. A plain 'Requires:' does not *guarantees* such an order. > > > > I understand / already thought as much, but in essence this means that you > require the crontabs package so why not just replace these 3 lines: > Requires(missingok): crontabs > Requires(pre): %crontabdir > Requires(postun): %crontabdir > > with: > Requires: crontabs > Because with a transaction that includes the removal or addition of crontabs, unless (pre) and (postun) are used this could get installed prior to crontabs and thus you run into the chicken before the egg syndrome. If the other package contents need to be on the file system before this package can install, and need to remain on the file system until after this package is removed, then it needs (pre) and (postun) requirements. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.