Hi, Just wanted to let you guys know that we are introducing some intrusive changes in what will most likely become packetfence 2.0.2.
- Module versioning for pf::vlan::custom and pf::radius::custom We are now relying on module versioning to catch interface changes before they hurt the users. PacketFence will generate errors on startup if you have not upgraded your modules' interface and version. - Removed conf/templates/*.pl captive portal extensions This mechanism was removed since the new pf::web::custom mechanism is cleaner and less error-prone. Any custom code in release.pl, login.pl, enabler.pl, redirect.pl, scan-in-progress.pl, error.pl, status.pl and register.pl won't be executed anymore. - pid files changed location Previously in var/ they are now in var/run/ - New configuration directory for generated configuration: var/conf/ Changed the location of the generated configuration file from conf/ to var/conf/. This will mitigate the fact that people were trying to modify the generated files instead of the templates. This is not an indication that we are about to release 2.0.2 but just to let you know what went in lately. Let us know what you think about it. Cheers! -- Olivier Bilodeau obilod...@inverse.ca :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Packetfence-devel mailing list Packetfence-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-devel
