GitLab

Save the triggers for later execution

pkg triggers will run them

When a remote repo reports multiple time the same package which could
happen in case the same package do exist with multiple extension or hash

Deduplicate the dependency loading chaing to avoir useless warning

capsicum sandbox prevent opening a file if an element in its path is
an absolute symlinks to a directory.

Another benefit is we can now use the pkg.exec within scripts

This documents the changes introduced in
25943330
as requested in issue #1116.

This enables the triggers to run scripts using most of the pkg.*
functions

It it useful to run pkg.exec for example

while here: update manpage after the removal of @*exec

@*exec will now on be directly implemented in the ports tree

for historical reason +DISPLAY was parsed first to ensure it takes
precedence over any message in the +MANIFEST to avoid the message
to be overriden later.

Since the messages has been switch to ucl files, all messages are
appended so there is no needed anymore for this backward compat.

Moreover it was preventing the variable expansions to happen because
the pkg structure was not yet defined

When processing the right side of a two compare the sign could be
improperly set to the left side sign varible when using <= >= or ==.

Clang11 supports the flag.

Needs to be part of the same shell command

This should help find uninitialized variables. Not enabled on FreeBSD
yet since I'm not sure if the FreeBSD11 Clang is new enough.

There are some additional UBSan warnings with newer Clang that need to be
fixed first.

If p->prefix is empty, we end up using -1 as the index.