format to ${PKGDIR}/(class).login, this also allows getting rid of the
LOGIN_CONF variable so that no Makefile changes are needed, only adding
the @sample.
Since version 0.16.0 released in February 2021, Netshot requires the
GraalVM JRE in order to run JavaScript and Python. GraalVM is not
available in ports. It is better to delete Netshot from ports than to
ship an outdated version with old Java libraries.
OK sthen
(misses the fragment dispatch)
generalize "tweak_other_paths" to run *after* the normal recognition, since
ocaml paths are linked in more generic ways that just "parent directory for
fonts", so they don't necessarily occur in the right order, and we shouldn't
care.
the symbol changes in libcompiler-rt.a for emutls are causing problems
and at least 250 packages maybe affected so this is the most sensible
way (we were overdue a bump to this anyway after other toolchain
changes, it's better if people are running code built with current
toolchain rather than a mixture).
discussed with robert@ tb@ espie@ naddy@
Export some ExtUtils::MakeMaker and Module::Build recognized environment
variables so they are picked up even if we don't run the configure
script directly.
This is useful for things that are not perl modules themselves, but include
perl modules, some of which seem to configure them at build time instead
of configure.
This is the first step to moving perl to have a vendor lib that
ports install into that is separate from where CPAN will install things.
Thanks to kmos@ for a bulk build that didn't turn up anything untoward
as discussed with sthen@)
also: kill some special useless casing... the regexp for adding
REVISION/EPOCH at the right location works with and without flavors
(no difference shown on make show=PKGNAMES through a full tree)
comes from REVISION and EPOCH properly. The most crucial check is probably
checking the end "flavor_ext" indeed comes from flavors (with the notable
exception of MULTI_PACKAGES' default FULLPKGNAME, as per ispell)
better to install all sets by default, even though this makes the chroot
more costly (slightly).
So hard-code them for now, grabbing them off SHA256 is on the TODO list
from gettext, to add a few more gettext scripts that we see sometimes, and
to add asciidoc. (has been in i386 bulks for months and forgotten about!)
ok espie, "I'm fine with the gettext-tools part and have no opinion on asciidoc" naddy@
Add powerpc to LLD_ARCH, and bump _SYSTEM_VERSION-powerpc so people
will upgrade to lld-linked packages when they exist. Remove
-Wl,--relax from several ports; ld.bfd needed this flag, but ld.lld
can't take it.
lang/gcc/8 needs USE_LLD = No, because LLD can't link C++ code from
gcc (error: relocation refers to a discarded section: ...), and also,
the adastrap is too old.
To avoid linker errors on macppc, you need a snapshot where
/usr/bin/ld is LLD.
ok sthen@
- Add a version argument (second) to modgo-gen-modules-helper.
- Change modgo-gen-modules target to fetch module info for the
current MODGO_VERSION of a port. Setting MODGO_VERSION=latest
will fetch the latest version the Go ecosystem knows about.
Similarly, if MODGO_VERSION is empty, fetch the latest
verstion Go knows about.
While here:
- Add '-trimpath' to MODGO_FLAGS.
OK danj@
If we don't clean, then the upcoming make build won't notice any changes
that we actually added to the Makefile, such as setting the CONFIGURE_STYLE
to "modbuild tiny".
Noticed by Mischa <obsdml () high5 ! nl>
skeleton script for people who want to override FETCH_CMD but don't
know exactly what ftp(1) options pkg_add/bsd.port.mk/dpb are going to
want.
A bit of feedback from sthen@, more to come most probably
clean at the end of a build.
Add a new global config option: NEVER_CLEAN
so that no path ever gets cleaned (to be used ONLY if you have lots of disk
space).
I've actually done this manually in the past, to test various tools on
lots of objdirs...
These were previously used to automatically add tags to PLIST for
Haskell library ports. Since library ports no longer exist, such
tagging only ever triggers for ghc package where it is now harmful.
ok kili
While here try using @v/list first, if that fails use @latest. This should
fix some of the "not being able to see the latest version" issues that
happen when upstreams re-tag.
Tweaks / OK from afresh1
human-readable way, and compare them, so that people can figure out if
the version parsing did cope with whatever scheme upstream came with.
should alleviate the need for EPOCH in many cases
- fix an old optimisation that was lost, namely do not run distpatch
if it's not necessary
nothing broken after 3000 ports built, so it's unlikely to have any negative
side-effect
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
In some cases (mostly with insane distnames from local test builds, but
conceivably also possible with long combinations of flavours) they can
exceed the character limit. Discussed with espie@ who pointed out that
plist_db doesn't include entries for debug packages.
From Mikolaj Kucharski.
check. Newer ccache uses cmake making it impractical to break the loop by
just disabling ccache for the individual ports on the way to building ccache.
binaries for packages using DEBUG_PACKAGES. This avoids the current
situation where a backtrace is useless (function names all "??") if
a package was built with DEBUG_PACKAGES but the debug-foo package is
not installed. ok espie@ pirofti@
(a ten year old network daemon, no longer maintained in ports or upstream;
distfiles were fetched from debian who removed it from their packaging ~5
years ago). py-tagpy is one of the few consumers of boost's py2 library.
ok jca
everything so that people updating from subsequent snapshots won't
have old clang 8-compiled packages lying around.
also will work around the problem where packages don't have WANTLIB
in sync, in some cases these have an unlisted dependency on libc++
which won't have been updated as needed (found by matthieu@).
ok ajacoutot@
we rerun pkglocate
also check the pkglocate cookie vs the fake cookie, so that we rerun things
if somehow fake was rerun without cleaning things first (unlikely, but still)
