On Sat, 16 Aug 2025, ASSI via Cygwin wrote: > Jeremy Drake via Cygwin writes: > > I was trying to clean up my workflows now that llvm 20.1.8-2 is published, > > and I came across another possible setup bug. It seems that the -P option > > doesn't accept a package name that is provided rather than being the > > actual name of a pacakge. > > > > llvm20.1-devel is provided by llvm-devel 20.1.8-2, but passing that to -P > > results in the message: Package 'libllvm20.1-devel' not found. However, > > libclang-devel 20.1.8-2 requires libllvm20.1-devel, and selecting that > > version results in "Install libllvm-devel 20.1.8-2 (automatically added)", > > so requires does respect provides. > > Sorry, but it seems you're misusing provides
Quite possibly, I'm still trying to figure things out ;) > (and I'm not clear on > whether there should be any dots in the names of provides, but I think > it's best avoided). Provides are meant to guide dependency resolution > among a group of packages that belong together, not as an alias for the > install package. It's the installed base package that delivers a > provide that ensures that the versions are compatible, so it does not > make sense for each and every package to have their own versioned > provide, which would imply that one could mix and match between say, lld > and llvm-devel versions. Regardless, BUILD_REQUIRES is documented to allow provides, and scallywag passes BUILD_REQUIRES entries to setup -P, so there's a bug in there somewhere. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
