#175: Request for a Complete Tarball Including Submodules for FreeBSD Port Update
-----------------------+--------------------------------------
Reporter: ehaupt@… | Owner: pulkomandy
Type: defect | Status: new
Priority: major | Milestone: 3.0
Component: GrafX2 | Version: 2.9
Resolution: | Keywords: tarball freebsd port src
-----------------------+--------------------------------------
Comment (by ehaupt@…):
Thank you for clarifying. I've reviewed how GrafX2 builds from the `src/`
directory and found that it uses `curl` commands in the `Makefile` to
automatically fetch the latest versions of dependencies from URLs. This
keeps the software up-to-date with the latest libraries, which is
beneficial during development.
However, such network operations during the build process are problematic
because they conflict with the guidelines in the FreeBSD Porter's
Handbook. This issue extends beyond FreeBSD, as many other systems that
package software from source also disable network access in sandboxed (1)
build environments to ensure security and stability. This means that any
attempt to access the network during the build will fail in these
environments.
For release source tarballs, it’s crucial to avoid network operations and
pin dependencies to specific versions to ensure consistent, reliable
builds. This approach aligns with best practices for software
distribution, helping maintain a predictable and secure build process.
(1)
https://docs.freebsd.org/en/books/porters-handbook/quick-porting
/#porting-testing
--
Ticket URL: <
http://pulkomandy.tk/projects/GrafX2/ticket/175#comment:2>