I suspect package compatibility is not maintained on per-pfSense-version basis. Meaning, packages worked on 2.x up until the package changes on 2.3, and probably will work on into the future until the next breaking change.
https://doc.pfsense.org/index.php/Upgrade_Guide#pfSense_2.3_Upgrade_Guide has text: See Package Port List for a list of packages currently available on 2.3. Links to -> https://doc.pfsense.org/index.php/Package_Port_List Also, from the blog entry on the 2.3.1 release: https://doc.pfsense.org/index.php/2.3_Removed_Packages -- Steve Yates ITS, Inc. -----Original Message----- From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Bryan D. Sent: Friday, June 17, 2016 5:18 PM To: pfSense Support and Discussion Mailing List <list@lists.pfsense.org> Subject: Re: [pfSense] How to determine supported packages without installing On 2016-Jun-17, at 2:35 PM, compdoc <comp...@hotrodpc.com> wrote: > I think this is complete: > <snip'd> Thanks. Looks like I can proceed with an update to 2.3. Regardless, I still think there should be a way to authoritatively determine this info via the pfSense web site -- ideally, for all releases, minimally for the current release. Perhaps the generation of such a page could be added to the build/release tools? Alternatively, porting pfSense's packages pages to run on the pfSense site could provide the current-release info. _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
