Let's say I am done modifying a codebase and now am ready to give it a try. Is there an accepted make/install sequence I am supposed to follow? It is perl… no need to compile anything or whatnot. You may want to run ‘make devel’ to replicate an rpm installation but only from source (doing stuff that the packaging is doing)
It looks like PF is expected to be installed into /usr/local/pf. Is there an install script that is supposed to do it for me? You can simply create a symlink /usr/local/pf that points to your devel dir… make sure not to overwrite your actual PacketFence installation if you are working on the same box. Cheers! dw. -- Derek Wuelfrath dwuelfr...@inverse.ca :: +1.514.447.4918 (x110) :: +1.866.353.6153 (x110) Inverse inc. (www.inverse.ca) :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) On June 2, 2015 at 11:30:24, Boris Epstein (borepst...@gmail.com) wrote: Derek, One more question. Let's say I am done modifying a codebase and now am ready to give it a try. Is there an accepted make/install sequence I am supposed to follow? It looks like PF is expected to be installed into /usr/local/pf. Is there an install script that is supposed to do it for me? Thanks. Boris. On Fri, May 29, 2015 at 2:27 PM, Derek Wuelfrath <dwuelfr...@inverse.ca> wrote: Boris, 1. Any conventions as far as forking/branch names? Whatever floats your boat… it is in your repo so we don’t really care about it ;) 2. Got it - I just use my local repo as my sandbox. Are there any conventions in the PF community as far the IDE to use, the ways to setup test scenarios, etc? You are talking about coding Perl… most of us are using VI or emacs as an “IDE” ;) 3. Self-explainatory. I guess git pull in this case is the accepted merge mechanism, right? Github offers pretty good documentation on how to create a pull-request from a fork :) Cheers! dw. -- Derek Wuelfrath dwuelfr...@inverse.ca :: +1.514.447.4918 (x110) :: +1.866.353.6153 (x110) Inverse inc. (www.inverse.ca) :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) On May 29, 2015 at 10:41:08, Boris Epstein (borepst...@gmail.com) wrote: Derek, Thanks! 1. Any conventions as far as forking/branch names? 2. Got it - I just use my local repo as my sandbox. Are there any conventions in the PF community as far the IDE to use, the ways to setup test scenarios, etc? 3. Self-explainatory. I guess git pull in this case is the accepted merge mechanism, right? Cheers, Boris. On Fri, May 29, 2015 at 9:32 AM, Derek Wuelfrath <dwuelfr...@inverse.ca> wrote: Boris, 1. Fork the PacketFence repo from Github. (https://github.com/inverse-inc/packetfence#fork-destination-box) 2. Do the changes in your forked repo of PacketFence 3. Submit a pull-request ! Cheers! dw. -- Derek Wuelfrath dwuelfr...@inverse.ca :: +1.514.447.4918 (x110) :: +1.866.353.6153 (x110) Inverse inc. (www.inverse.ca) :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) On May 28, 2015 at 17:28:05, Boris Epstein (borepst...@gmail.com) wrote: Hello all, I am considering going over the PF code and trying to fix some issues I am encountering. So I am wondering what the procedures are for introducing the changes - i.e., git labeling/branching conventions, etc. Thanks. Boris. ------------------------------------------------------------------------------ _______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
