3 ms·
> Is the installation stateless (no scriptlets/lifecycle scripts)? I feel like the reason `npm`/the node.js ecosystem has these is because... as soon as you w
by MuffinFlavored 8y ago
> Is the installation stateless (no scriptlets/lifecycle scripts)?
I feel like the reason `npm`/the node.js ecosystem has these is because... as soon as you want to do anything serious, you need them.
How else do you build native modules across different platforms, run initial post-installation configuration scripts, etc.?
- numbsafari 8y agoYou make it declarative instead of scripted. Scripts aren’t truly platform independent. You’ll branching logic for different platforms. Why not capture that with different declarative structures for each platform? Running scripts as part of software install is something we, as an industry, need to solve.
- moosingin3space 8y ago> How else do you build native modules It is my understanding that wasmer is trying to create a new ecosystem that doesn't rely on native modules. > run initial post-installation configuration scripts It's been my experience, as a long-time Linux user, that this is actually a bad thing. Stateless systems are far easier to work with -- a package manager can be far faster and simpler if it just extracts an archive. I can't think of a single case where post-installation configuration scripts couldn't be replaced by something simpler, using the filesystem.
- orf 8y agoDownloading a dependent native library from an official source, based on the current OS version.
- moosingin3space 8y agoCould this not be done though the dependency system itself, if it were sufficiently generic?