On Wednesday 20 July 2011 14:37:35 Ratan Sebastian wrote:
A little middle of the week update to make up for last
have been some major changes with ssc. The command line parsing has
been completely overhauled. The ArgumentParser that I'd written was
far too buggy and has been switched out for thor. Besides the
stability that thor provides, it also adds a lot of useful features
right out of the box like command help. You can do ssc help [command]
and ssc [appliance|package|...] help for more specific help
to get information about any of the commands and the options that it
allows and which options are required and which are optional. It also
provides helpers to nicely format output and error messages.
By the end of this week you can expect to see the
commit, status and
update commands implemented.
Are they working from within an appliance on the actual state of the files,
packages, etc. Or is this purely working on the cached data?
So, if for example I build an openSUSE JeOS appliance, run it somewhere, add
more software in the running system with zypper, does ssc allow me to easily
add this software to the appliance configuration?
Also the errors that you might have gotten if
you'd tried ssc earlier
must be fixed now if you update the studio_api gem. I've made a minor
version bump that includes studio_api v3.1.2 as a dependency.
It would be great, if you could put the gem on rubygems, so that people can
just install it with "gem install ssc" without having to do any other
configuration or know any URLs. This would make it easier to try it and get
feedback. Do you think you could do this?
It also would be nice, if you could present your project on the studio-
users(a)suse.de mailing list. There you can get more feedback from other Studio
users, and it's a better place to discuss technical details than the opensuse-
project mailing list.
Cornelius Schumacher <cschum(a)suse.de>
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org