Daryl F wrote in <b3b765a6-1ff7-2a75-58d9-84c03b1455fb@prairieturtle.ca>: |On Wed, 24 Apr 2024, John McQuah wrote: ... |system. For me I consider a MISSING file at pkgmk time is fatal. I don't |mind NEW because it usually means I've already installed something that |autoconfigure or friends found and added support for. I concur a hundred percent. ... |I recall the discussion about optional dependencies. I was neither for or |against it. Some might find it useful to automatically include them but I |just review the ports and manually install an optionals I like. Yes. An option would possibly be a syntax like the VERP system of SMTP / mailing-lists, ie, you give the optionals as part of a name, and the new prt-get would fail if the mentioned optionals would not be mentioned in the Pkgfile, but otherwise do the necessary steps. Eg the core port ninja (unfortunately) has # Optional: bash-completion zsh so you could install ninja,zsh or ninja,zsh,bash-completion or ninja,bash-completion,zsh, and the new prt-get would note the used optionals in the DB, too. So then prt-get update ninja would effectively mean what was used. And if the Pkgfile had changed in the meantime and zsh would no longer be Optional:, you had to uninstall first to get that updated. Packaging systems are very, very complicated beasts. Anyway i hope that "prt-get isinst" is anything necessary in the runnable code of Pkgfile's. Good night from Germany, --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)