Open MrcSnm opened 2 years ago
absolute paths are not portable and will break on other people's machines once you publish your package, is there a reason why you need an absolute path and can't do it with a relative one?
There isn't any real reason for that, but I don't think there is a reason for blocking it, specially that it is not everyone who wants to publish their packages.
System information
Bug Description
core.exception.AssertError@source\dub\internal\vibecompat\inet\path.d(222): Trying to append absolute path.
How to reproduce?
Add absolute path to sourcePaths
Expected Behavior
Is there any real reason to not accept the absolute path?
Logs