In relation to: https://github.com/meteor/windows-preview/issues/1
I’m looking for a way to work with packages in a way that will work on both Windows and Unix-flavoured platforms. Here’s roughly the process I’m following, using iron:router as an example:
mkdir -p vendor/packages
git clone https://github.com/iron-meteor/iron-router.git iron:router
meteor add iron:router
- (rinse, repeat for every package we’re using)
All well and good on the dear old Mac! But our team also works on Windows. Because the semi-colon is illegal in a filename on Windows, I have worked around the issue as follows:
- Clone everything as above, replacing ‘:’ with ‘-’
- Where required, add to each package’s
Package.describe()with a name, e.g. ‘iron:router’, as described in the attached issue.
The bit that I don’t like, as you might have guessed, is that I’m effectively having to patch other peoples packages.
So I guess my questions are:
- Is there another way that I’m missing?
- Is there perhaps an improvement on the way for this? I was wondering whether perhaps the
Package.describe()could be a required parameter to aid cross-platform development.
Thought it might be useful to know why I’m trying to do this in the first place, so here goes:
- My company requires we store all third party code internally for security
- In CI, we want third party code to be utterly guaranteed to be the same, so it’s under our SCM along with everything else that we’ve written.
- We’re interacting with a large C++ codebase which grew up in a Windows world, and so is very difficult to port to another OS, like Linux, (as desirable as that might be I might add!). Windows support is therefore a must.
Thanks for reading,