-4.1.2 (?? May 2022)
+4.1.2 (?? Nov 2022)
[BUG FIX] Packages for which the flavor mechanism is newly introduced sometimes had their old packages remain as conflict.
+[BUG FIX] As of OS version 13, the specification change of grep(1) caused "empty (sub)expression" errors resulting in wrong processing at many points.
4.1.1 (20 April 2022)
[IMPROVED] Adapt to the specification change of pkg-create(8) that the default extension of the package files become "pkg".
[IMPROVED] Adapt to the behavior change grep(1) as of 12.0-RELEASE that the case distinction is ineffective in some locale, which as a result prevented the execution by users in such locales.
MYVERSION=4.1.2
COMPATIBLE_VERSIONS='^(4\.[1]\.[0-9])$'
# Template for development versions
- MYVERSION=4.1.1+toward_4.1.2_20220508155922
- COMPATIBLE_VERSIONS='^(4\.[0-1]\.[0-9]]|4\.[0-1]\.[0-1]+(|\+toward_4\.[0-1]\.[0-9]+_[0-9]+))$'
+ MYVERSION=4.1.1+toward_4.1.2_20221112165132
+ COMPATIBLE_VERSIONS='^(4\.[0-1]\.[0-9]]|4\.[0-1]\.[0-1]+\+toward_4\.[0-1]\.[0-9]+_[0-9]+)$'
}
# ============= Parse options, arguments and control parameters =============
# ============= Get the extended regular expression pattern of ports for pkg(8) =============
pkgsys_pkgtools_ports_filter_regexp ()
{
- echo '^ports-mgmt/(pkg|pkg-devel)(|@.*)$'
+ echo '^ports-mgmt/(pkg|pkg-devel|pkg@.*|pkg-devel@.*)$'
}
# ============= Get the extended regular expression pattern of package names for pkg(8) =============
| env LANG=C grep -m 1 '^pkg-[0-9]'` || :
[ -n "$pkgname" ] && pkg_inst_remote_wild "$pkgname" && return
message_echo "INFO: Failed by package, so installing pkgng by port."
- env LANG=C grep -Ev '^[[:space:]]*WITH_PKG(|NG)=' /etc/make.conf > ${TMPDIR}/make.conf 2> /dev/null || :
+ env LANG=C grep -Ev '^[[:space:]]*(WITH_PKG|WITH_PKGNG)=' /etc/make.conf > ${TMPDIR}/make.conf 2> /dev/null || :
echo WITHOUT_PKG=yes >> ${TMPDIR}/make.conf
echo WITHOUT_PKGNG=yes >> ${TMPDIR}/make.conf
dev_out=/dev/stdout
fi
done
fi
- glob_regexp_allflavors=`echo "$glob_regexp" | sed 's/$$/(|@.*)$/'`
+ glob_regexp_allflavors=`echo "$glob_regexp" | sed 's/$$/@.*$/'`
{
pkg_info_all_flavored_origins
cut -f 2 "${DBDIR}/installed_ports:pkg_vs_origin.tbl" 2> /dev/null
- } | env LANG=C grep -E "$glob_regexp_allflavors" 2>&1 || :
+ } | env LANG=C grep -E -e "$glob_regexp" -e "$glob_regexp_allflavors" 2>&1 || :
else
if expr "$glob" : '[a-z][a-zA-Z0-9_.+-]*[a-zA-Z0-9_.+]$' > /dev/null 2>&1 && \
[ `expr "$glob" : '.*-[0-9]' 2>&1` -eq 0 ]
glob_pattern=$1
{
pkgsys_eval_ports_glob "$glob_pattern" 2> /dev/null || :
- echo "$glob_pattern" | env LANG=C grep -E '^[a-z]+/[a-zA-Z0-9_.+-]+(|@[a-zA-Z0-9_.+-]+)$' || :
+ echo "$glob_pattern" | env LANG=C grep -E '^[a-z]+/([a-zA-Z0-9_.+-]+|[a-zA-Z0-9_.+-]+@[a-zA-Z0-9_.+-]+)$' || :
} | env LANG=C grep -v -e '^$' | sort -u
}
Here, the evaluation of the bracket is actually done by passing it to an extended regular expression by simply converting the prefix "[!" to "[^".
A glob is recognized as a unique name (package name without the version part) if no slash "/" or any special character for an extended regular expression or a shell\-type glob is included in the pattern.
For example, all of "zip" "zip\-3.?", "zip\-*", "zip\-[0\-9]*" and ":^zip\-[[:digit:]]+\.*" can match "zip\-3.0"; "archivers/unzip*" can match both of "archivers/unzip" and "archivers/unzip\-iconv".
-When the \fIglob\fR should match the all flavors of a port, a regular expression can be used such as ":devel/py-setuptools(|@.*)".
+When the \fIglob\fR should match the all flavors of a port, a regular expression can be used such as ":devel/(py-setuptools|py-setuptools@.*)".
.SH ARGUMENTS
One of the following \fIcommands\fR can be given for optional operations or confirmation.
.TP