Please have a look to: http://www.novell.com/documentation/webyast/book_webyast_vendor/?page=/docum... This should also work with config files. (I have never tested) cause: http://www.novell.com/documentation/webyast/book_webyast_vendor/?page=/docum... works too. Greetings Stefan Am 03.08.2010 10:36, schrieb Jiri Suchomel:

[sorry if you get this twice, I have some problems sending mails]

Hi!

We've just discussed with Ladislav how vendors should properly customize their appliances. The question is not about the files that need to be changed (these are described e.g. at [1]) but about proper delivery of the modified files.

For example, Ladislav has created webyast-slms-branding package [2], which provides modified versions of some config files (like basesystem.yml for SLMS 'firstboot' workflow). However, installing such package brings conflicts with the files that are already installed (default basesystem.yml is part of webyast-firstboot-ws package).

I see two possible solutions:

1. branding packages provided by vendor should not install their config files directly, but to some special subdirectory and copy them to correct location in post-install scripts: something similart that is done with sysconfig values. Such solution should be documented, so vendors know how to create branding packages.

2. we should not install such config files (basesystem.yml, control_panel.yml, eulas.yml) in our webyast packages directly to their target location (/etc/webyast), but only as example files: either to specific directory (e.g. /usr/share/doc) or with specific extension (/etc/webyast/basesystem.yml.example). With this way, vendor could more easily package their customized config files. On the other hand, we'd need to adapt some of our webyast packages to reflect this change into ATK 1.1.

Opinions?

[1] http://www.novell.com/documentation/webyast/book_webyast_vendor/?page=/docum...

[2] https://build.suse.de/package/show?package=webyast-slms- branding&project=home%3Alslezak%3Abranches%3ADevel%3ASLMS%3A1.1

-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

* Jiri Suchomel [Aug 03. 2010 10:36]:

I see two possible solutions:

1. branding packages provided by vendor should not install their config files directly, but to some special subdirectory and copy them to correct location in post-install scripts: something similart that is done with sysconfig values. Such solution should be documented, so vendors know how to create branding packages.

2. we should not install such config files (basesystem.yml, control_panel.yml, eulas.yml) in our webyast packages directly to their target location (/etc/webyast), but only as example files: either to specific directory (e.g. /usr/share/doc) or with specific extension (/etc/webyast/basesystem.yml.example). With this way, vendor could more easily package their customized config files. On the other hand, we'd need to adapt some of our webyast packages to reflect this change into ATK 1.1.

Properly packaging branding was somehow missed, thanks for bringing this up ! Since this is mostly about moving files from one package to another, I'd consider this low risk but with a high value. Having SLMS as a WebYaST consumer gives us a good opportunity of having the 'customer next door'. Please work with the SLMS team to fulfill their requirements. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

On Tue, Aug 03, 2010 at 03:58:52PM +0200, Jiri Suchomel wrote:

Dne úterý 03 Srpen 2010 11:17:48 Stefan Schubert napsal(a):

...

Please have a look to: http://www.novell.com/documentation/webyast/book_webyast_vendor/?page=/docum...

This should also work with config files. (I have never tested) cause:

No, this is only designed to work with the files that are served to the user: http://gitorious.org/opensuse/yast-web-client/commit/d9ecd2097af7229027cf8d8...

...

http://www.novell.com/documentation/webyast/book_webyast_vendor/?page=/docum...

And this is for translations. Both are ideas how it could be implemented for config files but it will not work for them now.

...

works too.

Well, I have somehow misinterpreted these links. Do you realy mean that for e.g. vendor's basesystem.yml should be located under /srv/www/yast/public/vendor? Do we have some logic that uses this file if it is found here?

How I understood your comment about 'vendor' directory:

1. Check for the file (e.g. basesystem.yml) under /etc/webyast/vendor/ 2. If it is not present there, check /etc/webyast location (= our default)

With this, vendors could save their config files into /etc/webyast/vendor/, while we can package our config files (as examples) under /etc/webyast.

This scheme makes sense in some cases: - Admin overrides a vendor library: /usr/local/lib/liberec.so /usr/lib/liberec.so - User overrides an admin config ~/.profile /etc/profile For our config files it would be perhaps also useful, but not necessary, as long as the code works with no config file at all (which I think it already does). Then we can use original proposal 2 and move the samples to /usr/share/doc/packages/$PKG/examples -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

Am 04.08.2010 10:48, schrieb Jiri Suchomel:

Dne úterý 03 Srpen 2010 17:54:41 Martin Vidner napsal(a):

...

On Tue, Aug 03, 2010 at 03:58:52PM +0200, Jiri Suchomel wrote:

...

Dne úterý 03 Srpen 2010 11:17:48 Stefan Schubert napsal(a):

...

Please have a look to: http://www.novell.com/documentation/webyast/book_webyast_vendor/?page=/ documentation/webyast/book_webyast_vendor/data/sect1_7_chapter_book_web yast_vendor.html

...

...

This should also work with config files. (I have never tested) cause:

No, this is only designed to work with the files that are served to the user: http://gitorious.org/opensuse/yast-web-client/commit/d9ecd2097af7229027cf8d 87a1bf62ea3574af7b

...

...

http://www.novell.com/documentation/webyast/book_webyast_vendor/?page=/ documentation/webyast/book_webyast_vendor/data/sect1_8_chapter_book_web yast_vendor.html

And this is for translations. Both are ideas how it could be implemented for config files but it will not work for them now.

...

...

works too.

Well, I have somehow misinterpreted these links. Do you realy mean that for e.g. vendor's basesystem.yml should be located under /srv/www/yast/public/vendor? Do we have some logic that uses this file if it is found here?

How I understood your comment about 'vendor' directory:

1. Check for the file (e.g. basesystem.yml) under /etc/webyast/vendor/ 2. If it is not present there, check /etc/webyast location (= our default)

With this, vendors could save their config files into /etc/webyast/vendor/, while we can package our config files (as examples) under /etc/webyast.

One reason why I added also this option is that we actually aready use /etc/webyast/vendor directory, at least for logs.yml file.

I do not know what was the reason for introducing this, or if it is used by chance.... does anyone know?

That has been more or less an "accident" which has not been intent. But perhaps it is an option now. :-) Greetings Stefan

Jiri

-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org