Bryan Fink wrote:
On Tue, 2004-03-23 at 10:46, Anas Nashif wrote:
Frank Steiner wrote:
Hi Anas,
7) The script feature again: It would be very nice if you could find a way to allow external scripts to be called directly from autoyast. This would help, because now you write post-install scripts, test them, edit them, then insert all the code into an xml file. Now, sth. goes wrong, you test again, and now the danger is that the script code in the xml file and the external script get inconsistent easily. Autoyast1 user to have that $I- Variable, pointing to the install source, so we just had created a SCRIPTS subdirectory unter the suse dir from the install source, and called all the scripts from there. Would it be difficult to add such a reference variable/tag in autoyast2, too? So that you can do anything on the install source, like call the scripts?
This works now, you can have the scripts anywhere using a new options named <location>. This can a URL supporting http/ftp/nfs just like with the autoyast= option while booting.
10) It would be nice if the value matched in a <match> tag in rules.xml could be referenced in the result section. Then one could e.g. match the IP in the match tag and use "profile-$ip.xml" as result. So with one rule you could add a special profile for each host by just adding a file "profile-xxx.xxx.xx.xxx.xml" in the profile subdir.
This is also available now:
something like that would work:
profile-@ip@.xml, not profile-$ip.xml as you proposed.
Anas
Two questions:
1.) Where are the these two abilities documented?
These abilities are not available to users yet, they will be available with SuSE Linux 9.1/SLES9.
2.) Is there any way to take this a step farther, and have the ability to reference the return value of a script in the result of the rule? So I could do something like run a script to ask "What is the name of the machine?", and then use the name the user types in to look up the autoyast file under that name.
Everything is possible, now however its a bit too late for the upcoming releases. I will note that down and see if it can be implemented for future releases. anas
...sorry this post is a little bit of a repeat of an earlier one of mine...
-Bryan