I have amassed a small collection of RPMs, from various sources, that I use and share with other team members. Instead of pointing them all to the different repositories and other sources to get them, we set up a shared directory through which people would just grab them and updated them as needed. Knowing that this was probably not the most efficient way to do this, and seeing how the person assigned to set up a ZLM server for the team to use failed at this miserably (he got a another machine for himself which was a plus for him I guess. But it has been almost a year and still no ZLM server!). To not step on any toes, and not needing all the functionality of a zlm server, I set up an open carpet server.

As soon as I let people know it was up, they come asking to use it. OES Netware has the ability to use red-carpet (the rug command line tool) to update rpms. (Anybody out there building rpms for Netware?) So to get this working for OES Netware you need to add it as a distribution in the distribution.xml file. Quite easy to do, just add:

<distro>
	<name>OES</name>
 	<version>NW65</version>
 	<arch>i386</arch>
 	<type>rpm</type>
 	<target>oes-nw65-i386</target>
 	<status>supported</status>
 	<detect>
		<file source="/etc/netware-release" substring="OES NW65" />
 	</detect>
</distro>

This will get you up and running. While OES Linux is based on the the same code as SLES 9. You should probably add something like the following to use open-carpet with it:

<distro>
	<name>Novell Open Enterprise Server Linux</name>
	<version>9</version>
	<arch>i586</arch>
	<type>rpm</type>
	<target>oes-linux-i586</target>
	<status>supported</status>
	<detect>
		<file source="/etc/novell-release" substring="Novell Open Enterprise Server Linux" />
	</detect>
</distro>

I will probably end up setting up a ZLM server any way as I have not discovered how to use open carpet to deliver patches from a YOU (YaST Online Update) server yet. (Which is what we are spending a lot of time testing right now.)

---