Louis,
100%. Makes perfect sense.
I actually subscribed to it and am awaiting moderation. Can you guys
authorize me?
Thanks.
Boris.
On Tue, Jun 2, 2015 at 5:40 PM, Louis Munro wrote:
>
>
> Gentlemen.
> We have an entire mailing list devoted to development (packetfence-devel).
>
> Make yoursel
On Jun 2, 2015, at 17:29 , Boris Epstein wrote:
> Derek,
>
> Just tried the symlink approach. For one thing, pfcmd is an executable that
> needs to be compiled - but that was easy.
>
> The hard part is, I get these failure messages now. Looks like the include
> paths are all out of whack for
Derek,
Just tried the symlink approach. For one thing, pfcmd is an executable that
needs to be compiled - but that was easy.
The hard part is, I get these failure messages now. Looks like the include
paths are all out of whack for some reason:
[root@pf1 ~]# service packetfence start
Starting Pac
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 t
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?
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,
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 m
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 (
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.
--
