is there a DOC_DEPENDENCIES variable and other Pkgsrc questions

lastflagstanding

Hello,
Pkgsrc newbie packager here with a few first questions:

The one in the title. There is BUILD_DEPENDENCIES for build time depencies, but is there one for documentation time? I didn't find how to conditionaly specify it in addition for documentation time, or set additional dependencies for dev environment, like one can do in e.g. Opam.
Are there secret sauces to keep (and automatize) up with new release for projects you package with Pkgsrc? Or are you all parsing Repology API?

Getting my feet wet on Rust repos, in a case I'm stuck at the distinfo step:

fetch: Unable to fetch expected file curl-sys-0.4.55+curl-7.83.1.crate
*** Error code 1

Stop.

I'm not a Rust user, but this package/combinaison is on crates.io, so I'm inferring problem is not on crates.io side, besides others crates are fetched without problem by Pkgsrc. Any idea?

Am I correct Pkgsrc "resolves" dependencies based on symlinks to select right versions of libraries/binaries at build time? In other words the only solution to solve runtime conflicts is to have multiple Pkgsrc "switches" (typically per project like with Npm, Opam, Poetry, etc.)?

Thanks for any help.

lastflagstanding Getting my feet wet on Rust repos, in a case I'm stuck at the distinfo step:

Yeah, that stupid crate name ..., have a look at e.g. net/piratebay/cargo-depends.mk file and tell cargo.mk where to fetch the source, in your case it would be

CARGO_CRATE_DEPENDS+=	curl-sys-0.4.55+curl-7.83.1
SITES.curl-sys-0.4.55+curl-7.83.1.crate+= ${MASTER_SITE_CRATESIO:S,^,-,:=curl-sys/0.4.55+curl-7.83.1/download}

lastflagstanding Are there secret sauces to keep (and automatize) up with new release for projects you package with Pkgsrc? Or are you all parsing Repology API?

I'd guess different people do it differently. Personally, I'm using news/tuifeed to get RSS/Atom feeds from upstream tags. Earlier I was using news/neix to do the same but, neix in no longer in development. Both use a configuration file to list the feeds you want to follow. Here's a short bit of my ~/.config/tuifeed/config.toml so you know what you actually need.

# tuifeed config.toml

[article-title]
show-author      = false
show-timestamp   = false

[sources]
"arqiver"        = "https://github.com/tsujan/Arqiver/releases.atom"
"asuka"          = "https://git.sr.ht/~julienxx/asuka/refs/rss.xml"
"badwolf"        = "https://hacktivis.me/git/badwolf/tags.xml"
"broot"          = "https://github.com/Canop/broot/releases.atom"
"castor"         = "https://git.sr.ht/~julienxx/castor/refs/rss.xml"
"citron"         = "https://git.sr.ht/~grtcdr/citron/refs/rss.xml"
"cchmod"         = "https://github.com/Dophin2009/cchmod/tags.atom"

you get the picture.

As for 1 and 4, I'm not sure what you are actually asking.

lastflagstanding

Thank you very much for the advice&tips, I will try that.

Regarding 1, I can maybe reword it like that:
With Opam I can specify in a package manifest dependencies which are for documentation, so that I can launch an opam ... command that will only install the executable and not its documentation (e.g. you may not want to pull a whole Haskell -> ... -> Pandoc & Ruby -> ... -> Asciidoctor compilation that your documentation.pdf require to build).
To my vague understanding, you can make this kind of distinction in Pkgsrc with BUILD_DEPENDS for dependencies only required for build time, hence my question:
is there an equivalent to BUILD_DEPENDS but for docs (sorry maybe I should correct the title with DOC_DEPENDS).
In the same way when working on a project, you may want to have executables&libraries installed only for development, e.g. Mypy for your Python project, which is something you can specify in Poetry "package" manifest, thus:
is there an equivalent to BUILD_DEPENDS but for dev time; i.e. something I could name DEV_DEPENDS ?

Regarding 4, I'm not quite sure how Pkgsrc does dependencies resolution, I will have to look a bit more into Buildlink. I guess I could reformulate my asking point with:
say you want to have exec A that require libo_v1 at runtime, and exec B that require the same library but with a different version libo_v2 at runtime, how would you set Pkgsrc for that ?

JuvenalUrbino

lastflagstanding With Opam I can specify in a package manifest dependencies which are for documentation, so that I can launch an opam ... command that will only install the executable and not its documentation (e.g. you may not want to pull a whole Haskell -> ... -> Pandoc & Ruby -> ... -> Asciidoctor compilation that your documentation.pdf require to build).

Yes, you can rely on package options and configure an optional ``doc build option for your package, by writing a options.mk file to put in the package directory, like:

PKG_OPTIONS_VAR=	PKG_OPTIONS.pkgname
PKG_SUPPORTED_OPTIONS=	doc
PKG_SUGGESTED_OPTIONS=	# empty
PLIST_VARS+=		doc

.include "../../mk/bsd.options.mk"

.if !empty(PKG_OPTIONS:Mdoc)
BUILD_DEPENDS+=		asciidoc>=8.3.3:../../textproc/asciidoc
CONFIGURE_ARGS+=	--enable-asciidoc
PLIST.doc=		yes
.else
CONFIGURE_ARGS+=	--disable-asciidoc
.endif

See Chapter 16. Options handling.

lastflagstanding Regarding 1, I can maybe reword it like that:

Ahh ... now I get it. See @JuvenalUrbino answer, you can do this with options.mk.

lastflagstanding Regarding 4, I'm not quite sure how Pkgsrc does dependencies resolution, I will have to look a bit more into Buildlink

Yes, buildlink is where you want to look.

kim

I also like the way the git packages are split into git-base and git-doc, with a git meta package to install a useful combination of git packages. This allows minimal installs to just call for git-base and avoid the "overhead" of documentation.