Most of my homegrown libraries are private and are used locally for the most part. They are in ~/Projects/D/libs . Until now I've always used dub add-path and things worked fine. Updated my install am now getting this message:

     Warning Package at path '/home/soulsbane/Projects/D/libs/textrecords/' should be under '/home/soulsbane/Projects/D/libs/textrecords/$VERSION/textrecords'
     Warning The package will no longer be detected starting from v1.42.0

I'm guessing it's caused by this https://github.com/dlang/dub/pull/2610. What's the fix for this exactly? Thanks!

On Sunday, 25 June 2023 at 04:50:42 UTC, Soulsbane wrote:

A fix would be to do the following:

for package in $($HOME/Projects/D/libs/*); do
  mv -v $package $package/master/$(basename $package)
done

Provided that all you have in your libs folder are folders that represent packages.
This would also allow you to use different versions of a library (I'm assuming you only have one, hence the master), and work with libraries like Cybershadow's ae.
However, I'm not sure we should expect our users to do this for a simple add-path.

On Sunday, 25 June 2023 at 12:21:52 UTC, Mathias LANG wrote:

for package in $($HOME/Projects/D/libs/*); do
  mv -v $package $package/master/$(basename $package)
done

Yeah, each folder under libs is a package and it's own git repository. I think I'll just use the add-local approach. Kind of a pain but getting spammed with a page of warnings every compile is getting tiring :). Thanks a lot for the help Rikki and Mathias

On Monday, 26 June 2023 at 01:35:07 UTC, Soulsbane wrote:

If your packages are all in the same folder, you could also use path dependencies in your dub recipe, which saves the hassle of manually doing dub add-local on new systems and dealing with incompatible version tags:

	"dependencies": {
		"your-package": {"path": "../your-package-repo/"},
	},