Consider cross-platform changes

RamblingCookieMonster commented 8 years ago

A number of changes will need to be made to allow cross-platform support:

PSDependScripts will need changes. FileSystem could support both, or be renamed and aliased to something indicating it only supports Windows. If it remains Windows only, dependency types for xplat file system dependencies would be nice, but might be more painful than simply using UNC paths...
FileDownload dependency type should not use System.Net.WebClient
PSGalleryNuget dependency type should be removed, or adapted in some way to work on nix without nuget.exe, if no nuget binary is available for nix
Care should be taken to use Join-Path over concatenating path delimiters, Split path over splitting on path delimiters
Various other issues that will be uncovered when something like this is implemented.
Add option to inject common paths from other platforms here
Update tests to accommodate cross platform support
Add AppVeyor build details for cross platform CI

gjonespf commented 7 years ago

Very keen to see this lib working on PowerShell Core (e.g. on Linux). Will have to have a look and see if I can help on this at all.

RamblingCookieMonster commented 7 years ago

Awesome!

A few quick thoughts:

Detect platform and store in module variable ( e.g. During module import, detect platform. Not sure how to reflect platform or how granular though). Alternatively, detect 'capability', where a tool you depend on may exist independent of platform
PsDependMap.psd1 might benefit from schema update. Perhaps a whitelist of platforms or capabilities, and a blacklist of platforms or capabilities, for each dependency type

Any platform specific bits, e.g. Bootstrapping nuget, could be halted by platforms or capabilities

Cheers!

RamblingCookieMonster / PSDepend