On 08/30/2012 01:35 PM, Olivier Dumon wrote: > Hi. > Same problem with me. > > Another question : > I used the packetfence repo to do the install. > Can I use git to make update ?
Yes but I would not recommend doing so except for a staging server perhaps. I would advise to checkout tagged releases and not follow stable or devel otherwise breakage would be pretty much guaranteed, for example when we change the SQL schema. Even with tagged releases you will have to handle the eventual file conflict yourself with configuration divergence mostly. Pulling in branches like feature/ipset in such a setup would be a task for someone very skilled in git, perl and packetfence. Again, I don't recommend it but if you think you can pull it off, try it. > Maybe I can try the daily snapshot repo ? Yes but feature/ipset isn't there yet but it's coming. Another thing with the snapshots is that you must read the UPGRADE guide for changes every time you do a 'yum update' and if there are SQL schema updates, you need to do them right away and monitor if the updates are subsequently modified. If the only reason about using git or the snapshot is to get feature/ipset, grab a patch and apply the patch. That's definitely the simplest. Let me know if you have further questions or ideas to make that work more smoothly. Regards, -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
