On Friday 02 December 2005 17:43, Brian Elliott Finley wrote: > 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)
Could I build an initrd on another node than the client? For example on the master? In that case I might prefer to have the package as noarch, just in case the master is of different architecture than the client. systemimager-initrd_template-x86_64-$version.noarch.rpm makes sense, too, one needs to put the %Requires: lines inside %ifarch blocks. With multiarch setups one would have to install the additional packages manually. But if you _allways_ want to build initrd on the client, an arch dependent rpm is fine, of course. Regards, Erich ------------------------------------------------------- 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
