Mailinglist Archive: yast-devel (35 mails)

< Previous Next >
Re: [yast-devel] Proper packaging of WebYaST branding
  • From: Stefan Schubert <schubi@xxxxxxxxxx>
  • Date: Wed, 04 Aug 2010 11:29:41 +0200
  • Message-id: <4C593305.3020701@xxxxxxxxxx>
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:

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:

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
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

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. :-)


To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
List Navigation
Follow Ups