-
Notifications
You must be signed in to change notification settings - Fork 311
feature/debian #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature/debian #10
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are no SQL schema generated for every packetfence version, it's only if the schema was updated so this, while clever, won't work.
Ignore my comment. It's actually very clever and will work. I'm integrating that for the RPM version. :)
|
Other tasks
|
debian/rules
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does the rules file knows if it's doing pfdetect_remote or not?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It knows from the directory $(CURDIR)/debian/packetfence-remote-snort-sensor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
|
|
dropped the relvant patch from debian/patches/
- refactored allowed services and binary name lists into a global list and a regex built from it - renamed $exe to $binary to avoid confusion
This prevents at least one bug where freeradius would have been started on debian even if disabled. Also, daemon names will be consistent inside packetfence but proper binary names displayed too where relevant.
removed several patches from debian/patches/
permissions multi-line Depends
|
Rebased |
|
good to go! |
c'est prêt!