OPNsense Forum

English Forums => Development and Code Review => Topic started by: interfaSys on January 27, 2016, 11:07:16 pm

Title: How to keep track of changes in the ports tree?
Post by: interfaSys on January 27, 2016, 11:07:16 pm

I've just noticed that suricata isn't compiled with SIMD support per example and obviously the Makefiles have to be kept generic and can't be optimized for every architecture, so if we end up compiling all the packages using a custom make.conf, how do we get notified of updates?

Code: [Select]

# pkg version -Ivl"<"
pkg: Can't access /usr/ports/INDEX-10: No such file or directory
Do we have to recompile everything every time a new release is announced?

Title: Re: How to keep track of changes in the ports tree?
Post by: interfaSys on January 27, 2016, 11:12:45 pm

Just tested with portmaster and it tells me which packages need an update. Is there another way?

Title: Re: How to keep track of changes in the ports tree?
Post by: franco on January 28, 2016, 06:09:01 am

That's one of your options, yes. The other one may be portupgrade.

We rebuild all packages for all releases internally mostly to avoid having an inconsistent repository WRT build options, even though that pkg does a good job of figuring out if the repo and its deps are ok (shared library tracking).

Title: Re: How to keep track of changes in the ports tree?
Post by: interfaSys on January 28, 2016, 10:49:35 am

OK, thanks.

Title: Re: How to keep track of changes in the ports tree?
Post by: interfaSys on January 29, 2016, 12:06:26 pm

Since "-I" is for index, it's also possible to use simply

Code: [Select]

pkg version -vl"<"
It's just much slower.