Working with Packages on 2.3 and Converting to Bootstrap
-
@virgiliomi:
I noticed that ntopng is in the Google Docs list of packages, but when I check on my 2.3 box, it doesn't appear in the list. Just wondering if there's a reason why this is, or if it's just an oversight somewhere.
It's a work in progress. In order to accommodate ntopng we have to upgrade to rrdtool 1.4, but to get to that point in the base system we need to revamp our RRD code to work without the graph option so that we can avoid adding a couple hundred MB in dependencies. Once the base system RRD code is reworked then we can add ntopng to the packages.
-
I know that the more popular packages deserve priority but is there actually a defined process for reviewing and making packages available for install through the GUI? If that process exists, is it something that can be published?
My reason for asking is that I'm very much a fan of the postfix package and eager to test it out on 2.3. It would be nice to know its current progress through the process.
A package readiness spreadsheet, like the one that was available for 2.2 (I think), would be really useful. Maybe even shared with and editable by package developers/maintainers, so they could say where they're up to.
-
Look at the ToDo issue in GitHub https://redmine.pfsense.org/issues/5568
Then you can find the issue for any package that is in the process of conversion (or done).
As people progress on each conversion those issues should be kept up-to-date. -
I know that the more popular packages deserve priority but is there actually a defined process for reviewing and making packages available for install through the GUI? If that process exists, is it something that can be published?
We haven't defined that process yet.
A package readiness spreadsheet, like the one that was available for 2.2 (I think), would be really useful. Maybe even shared with and editable by package developers/maintainers, so they could say where they're up to.
See the first post in this thread, it already has a link to the sheet for 2.3.
-
If anybody could please pick up sarg, that would be great.
-
Bind package is needed too..
I'm happy to help test bind, if required.
At the moment, I'm holding off upgrading to 2.3 as I use bind for DNS. -
can we get LCDproc-dev added to the list of packages that need conversion?
I've spent a few hours looking at all this info, and looking at the code of 2.2.x packages and 2.3 packages and i'm totally lost.
This guy posted instructions on how to manually get it working on 2.3, but we really need a package.
-
please pfsense is 2.3.2 not package postfix & mailscanner. ????????????????????
-
I noticed pfsense has the freebsd ports tree in the git repo, so all these requests for binaries could simply be honoured by allowing people to compile ports on a pfsense box?
-
I noticed pfsense has the freebsd ports tree in the git repo, so all these requests for binaries could simply be honoured by allowing people to compile ports on a pfsense box?
Negative. Putting a compiler environment on a firewall is extremely dangerous.
-
well obviously there is a security risk if its implemented in a bad way, I see worse things on pfsense tho then a compiler. I was just thinking out loud on how to make this a whole lot more flexible in packages.
I been reading the documentation linked to from the first post and am left confused in regards to specific steps, e.g. if i am making a pkg to use on pfsense, is it ok to build on a FreeBSD box? or is it preferred to use the pre built FreeBSD binary? or is it required to use a special build environment?
Also is there a requirement for a pkg to have GUI integration?
-
Those are topics for a different thread.
-
so this topic is nothing to do with making packages for 2.3 as the topic title says?
-
This thread was specifically for people who were developing packages previously who needed information on converting existing packages for use on pfSense 2.3 in the new pkg and bootstrap framework. Not for general package creation questions.
