Benard and I are contemplating the packaging of SI 3.5+. We're trying
to make a decision about how the initrd_template files should be
packaged. Currently they're part of $boot_package.
Here are some options:
1) Create a new package, systemimager-initrd_template, and have
systemimager-client depend on it. only the arch for the client in
question would be necessary, and this would end up being an arch
dependent package:
systemimager-initrd_template-$version.i386.rpm (for example)
systemimager-initrd_template-$version.ia64.rpm (for example)
Actually, that one makes a lot of sense to me. Anyone have other
suggestions or comments?
Thus spake Bernard Li ([EMAIL PROTECTED]):
Hey Brian:
Perhaps the reason why the boot-standard requires the server, is such that you
can make sure the version of the systemimager-server you have installed is
correct?
Right now the requires line looks like:
Requires: systemimager-server >= %{version}
Let me know what you want to do.
Thanks,
Bernard
--
Brian Elliott Finley
Mobile: 630.631.6621
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
