Closed bahlo closed 10 years ago
This sounds good, although I could see apm install
supporting this file as an argument, does that sound reasonable?
Yes, sounds perfectly reasonable.
Or maybe make it the default and re-route the current (npm install)?
+1
Rather than following the Bundler-like Atomfile
convention (which i suspect implies a simplified package and version DSL) , I think we should probably just expect something formatted more like the dependencies section of a package.json
. Perhaps even CSON since other Atom config files are in that format.
'packages':
'bahlo-theme': '0.1.0',
'thedaniel-package': '*',
Well with the recent announcement of stars management I think we could use that for bundle installing.
File-based 'bundles' are still appealing though, because a set of stars is tied to a single user account. Yes, it would be super cool if there was a user out there that wanted to maintain their stars as e.g. the best setup for Go development, but it might be easier to collaborate / more stable if a community could just provide a file listing dependencies that describes their blessed Atom setup.
I agree with @thedaniel, people would add them to their dotfiles and you'll have everything at one place (incl. .atom
-folder, for example). It also feels better (at least for me) to have it checked into a CVS.
What do you think about a command like
apm bundle
which installs all packages listed in anAtomfile
?I'm willing to implement this, I just wanted to check if that's what you want or if you have other plans.
Here's my current workaround: apm_bundle.sh.