Searchable packages repository like npm/pypi/rubygems

[mklymyshyn]

We need to have clear decision about technologies we gonna use. I prefer to use something like Homebrew with simplified build process. Here is example of Homebrew Formula (ruby).

The basic list of commands to illustrate idea is:

• [ ] compy search <term> - search by term
• [ ] compy info package - show info about package and list of available versions
• [x] compy graph > packages.txt - put packages graph into text file
• [x] compy install -r packages.txt - install packages from text file generated by compy graph command.(compy install does that)
• [ ] compy remove <package> - uninstall particular package
• [ ] compy freeze to freeze dependencies

[mklymyshyn]

Basically what I mean: I'd like to have ability to make search query using syntax like compy search <term> and have output very similar to Ubuntu's apt-cache search <term> command. Format like jquery@<latest version> - jQuery is library to ....

[mklymyshyn]

@edjafarov , what do you think?

[edjafarov]

@joymax this is pretty nice set of commands. regarding compy install -r packages.txt we already have packages with versions defined in package.json [compy:dependencies/development]. But we probably need to stabilize deep dependencies. To do that in node npm shrinkwrap is used and npm-shrinkwrap.json file is predefined to freeze dependencies. It might be better way, what do you think?

regarding the search: component have it's own search[https://github.com/component/component#searching-for-components] where you need to add project to Components List wiki page to make it available to search. That feel weird though. But it is already implemented https://github.com/component/component/blob/master/bin/component-search so it could be pretty easy to implement in compy. At least until we will have/create better alternative.

[mklymyshyn]

@edjafarov ,

we already have packages with versions defined in package.json [compy:dependencies/development]. But we probably need to stabilize deep dependencies. To do that in node npm shrinkwrap is used and npm-shrinkwrap.json file is predefined to freeze dependencies. It might be better way, what do you think?

yeah, then we can do in next way. Forget about >packages.txt and move on with package.json. But with one difference - when you install package (compy install jquery@<version>) and it automatically add this package into package.json. And same thing with compy remove. Then it will solve annoying thing with adding packages via editing text file

[mklymyshyn]

About components search - let's try what is already exist. Maybe it'll work for us.

[edjafarov]

when you install package (compy install jquery@) and it automatically add this package into package.json.

actually that is how it works now. you can compy install component/jquery and you will see jquery in package.json next guy who will fetch the code can just type compy install to install all packages from package.json

[mklymyshyn]

great!

[mklymyshyn]

So we need only search through components