non port: www/aws/files/patch-src_core_aws-net.adb |
Number of commits found: 4 |
Saturday, 26 Jun 2021
|
11:35 Rene Ladan (rene)
*/*: Remove expired ports:
2021-06-23 www/aws: Uses EOL Python 2.7 via devel/gnatpython
2021-06-23 www/aws-demos: Uses EOL Python 2.7 via www/aws
2020-12-31 devel/gnatpython: Uses Python 2.7 which is EOLed upstream
619332f |
Tuesday, 23 Jun 2015
|
22:20 marino
Ada Framework: Switch to gcc5-aux, upgrade 6 packages at once
The transition from gcc-aux to gcc5-aux in the Ada framework has been
blocked by the inability to build gtkada3 and, once resolved, GPS (due
to tight locking with compiler).
A few days ago, Adacore made their annual release of their main libre
products, include GPS. However, some products were tightly coupled with
the recent compilers, so in order to upgrade, the compiler had to be
switched and dependencies require many ports to be upgraded at once:
* lang/asis
* devel/gnatcoll
* devel/gps
* x11-toolkits/gtkada3
* www/aws
* www/aws-demos
While the version upgrades were modest in most cases (gps, gtkada3), the
amount of work put into each port was significant. There are too many
improvements to mention here. A few include the removal of dynamic
package lists and incorporating gnatcoll into gps to avoid building it
twice. A private "exp-run" was done all on all 50+ Ada ports to ensure
they still build.
Also, a new argument was added to Uses/ada.mk, "run", that pulls in the
GNAT compiler as a run depends. This was necessary for GPS that will
not launch correctly without the compiler in place.
|
Saturday, 17 May 2014
|
21:21 marino
www/aws: Upgrade from 3.1.0.0 => 3.2.0.0
The templates parser was split out from AWS and due to quirk how
GPRBuild interacts with aggregate library projects, linking it as a
separate library was more than challenging. It would drop a library
exchange file (aws.lexch) in /usr/local/lib/templates_parser during
the linking process. Ports are not support to touch areas outside of
their work directory -- if they do, builders will notice and fail the
port. After hours of trying to get GPRLib to behave, I was reduced to
copying the *.ali files over to the work directory and creating a
custom gpr file to make linking legal. In the process, I noticed AWS
was linking back to work directory (sanity checks don't flag this yet)
so that was fixed the the custom "-R" option that I added to GPRBuild
a couple of years ago.
I had to create a custom aws.gpr file for lib/gnat, and it works really
well. Currently something like 238 of 243 tests are passing and the
failing ones are socket related and may looking for linux-specific
output in a couple of cases.
* Documentation is now based on Sphinx.
* A fixed package list has replaced the generated one (due to number
of options, this was a real chore to generate and validate)
* The option to generate only a shared library was removed. It was
confusing and not really useful. It produces static and shared
libraries by default, and the shared ones can be suppressed optionally.
* The FreeBSD-specific makefile was removed. The previous issue was
caused by the way the compiler was built which has since been fixed
* ASIS was added as dependency
* RUN_DEPENDS were defined (they were missing before)
* GNUTLS support was fixed. It requires version 3 now and does not
required gcrypt or openssl anymore which indicated a previous problem.
The aws-demos port had some missing files and other problems. It has
been updated at the same time. Note that the output directory has
changed from share/examples/aws-demos to share/examples/aws. A couple
of tests that were broken now build, and a new test was added.
This update comes straight from the latest repositories and was custom
packaged. The annual Adacore release was about 5 months old.
|
Sunday, 13 Apr 2014
|
11:41 marino
www/aws: Fix usage of aws in jailed environment
AWS has a sanity check that assumes that binding to the standard loopback
address of 127.0.0.1 is always possible, but this is not a good assumption
inside a FreeBSD jail. The result is that connection is success because
it adjusts the 127.0.0.1 address correctly on the fly, but the sanity
check is no longer valid. The provided patch changes the sanity check to
get the address rather than assuming 127.0.0.1.
PR: ports/188342
submitted by: Natacha Porte
Approved by: maintainer (myself)
|
Number of commits found: 4 |