On Wed, Jul 20, 2011 at 8:15 PM, Cornelius Schumacher <cschum(a)suse.de> wrote:
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?
There is no way to do this automatically right now but I'll add this
functionality soon. A task to query the package manager and mark all
packages installed on the current system for addition to an appliance.
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?
There's currently already an ssc on rubygems. It seems to be the old
version. I'll contact the maintainer and see if I can get this one up.
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.
I'll do that.
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