Summary: | pkgbase: Unset dependencies in some pkgbase packages | ||
---|---|---|---|
Product: | Base System | Reporter: | Martin <martin.jakob> |
Component: | misc | Assignee: | freebsd-pkgbase (Nobody) <pkgbase> |
Status: | Closed DUPLICATE | ||
Severity: | Affects Only Me | CC: | emaste, freebsd, markj, pkgbase |
Priority: | --- | Keywords: | patch, pkgbase |
Version: | CURRENT | ||
Hardware: | Any | ||
OS: | Any |
Description
Martin
2019-08-12 19:23:53 UTC
After adding this patch to /usr/src/release/packages/template.ucl --- template.ucl_ 2019-06-02 09:09:55.109358000 +0200 +++ template.ucl 2019-08-04 17:40:34.305308000 +0200 @@ -15,3 +15,9 @@ desc = <<EOD %DESC% EOD +deps: { + FreeBSD-%PKGDEPS%: { + origin: "base", + version: "%VERSION%" + } +} Almost all libraries are now depending on runtime, except: - liby - libpmcstat - libpam - libifconfig the "subpackages", e.g *-development, *-profile, however are depending on their root package. For example: liby-devlopment -> liby liby-profile -> liby etc. Also, the clibs subpackages clibs-profile, clibs-development,... are still standalone. i rebuilt my pkgbase repo with "make -j4 packages", this finished without error and a created jail with these packages startet without problem. -- Martin Hi, i want to revisit this ticket with a run of the script on an 13 system (). There are still some "standalone" packages namely these: "clibs"; "clibs-dbg" -> "clibs"; "clibs-dbg-lib32" -> "clibs-dbg"; "clibs-dev" -> "clibs"; "clibs-dev-lib32" -> "clibs-dev"; "clibs-lib32" -> "clibs"; "libcompiler_rt" -> "runtime"; "libcompiler_rt-dev" -> "libcompiler-rt"; "libcompiler_rt-dev-lib32" -> "libcompiler-rt-dev"; "libcompiler_rt-lib32" -> "libcompiler-rt"; "librpcsec_gss" -> "runtime"; "librpcsec_gss-dbg" -> "librpcsec-gss"; "librpcsec_gss-dbg-lib32" -> "librpcsec-gss-dbg"; "librpcsec_gss-dev" -> "librpcsec-gss"; "librpcsec_gss-dev-lib32" -> "librpcsec-gss-dev"; "librpcsec_gss-lib32" -> "librpcsec-gss"; "libthread_db" -> "runtime"; "libthread_db-dbg" -> "libthread-db"; "libthread_db-dbg-lib32" -> "libthread-db-dbg"; "libthread_db-dev" -> "libthread-db"; "libthread_db-dev-lib32" -> "libthread-db-dev"; "libthread_db-lib32" -> "libthread-db"; "liby-dev" -> "liby"; "liby-dev-lib32" -> "liby-dev"; You can see naming inconsistencies in some packages with "-" and "_". e.g. in libcompiler_rt-dev.ucl # # $FreeBSD: head/release/packages/template.ucl 364103 2020-08-11 08:42:24Z manu $ # name = "FreeBSD-libcompiler_rt-dev" origin = "base" version = "13.0.r364958" comment = "libcompiler package (Development Files)" categories = [ base ] maintainer = "re@FreeBSD.org" www = "https://www.FreeBSD.org" prefix = "/" licenselogic = "single" licenses = [ BSD2CLAUSE ] desc = <<EOD libcompiler package EOD deps: { FreeBSD-libcompiler-rt: { origin: "base", version: "13.0.r364958" } } Quick follow up: after changing the names of the libs in the ucl files sed -i '' 's/libcompiler-rt/libcompiler_rt/g' *.ucl sed -i '' 's/librpcsec-gss/librpcsec_gss/g' *.ucl sed -i '' 's/libthread-db/libthread_db/g' *.ucl the dependencies are correct. just "clibs" and "liby" are still free floating... The above mentioned naming inconsistencies in some dependencies is caused in the script generate-ucl.sh In Revision base r364009 the line pkgdeps="$(echo ${pkgdeps} | tr '_' '-')" was added. This is a problem for packages with an "_" in their names like libcompiler_rt-*.plist librpcsec_gss-*.plist libthread_db-*.plist *** This bug has been marked as a duplicate of bug 254797 *** |