As I understand it, the RPM name convention for Mandrake is something
like this:
package-name-<package version>-<buildversion>mdk.<processor>.rpm
where <package version> is the version of the program you're building,
<buildversion> is a builder-maintained version so that a rebuild of the
same product version can be handled as an upgrade without --force, and
processor is generall i586 or noarch in the case of non-compiled stuff
like perl scripts or font packages.
The mdk indicates that it is an OFFICIAL Mandrake package.
I could be wrong on any of this, but I *think* this is how it works.
- Theo
Vincent Danen wrote:
>On Sat Dec 01, 2001 at 01:18:01PM -0600, Timothy R. Butler wrote:
>
>> I was wondering about the naming conventions of RPM's on MDK. I am working
>>up a spec file to build Mosfet Liquid into an MDK rpm, but should the release
>>be a plain "1" or "1mdk"? I notice most Mandrake apps have the mdk appended
>>to the version, but should a third party packager use that too?
>>
>
>If you're making the spec specific to Mandrake, I would use the mdk
>extension. You'll notice that most other vendors (other than redhat) use
>an abbreviation of their product name for the extension, for example:
>
>Trustix: ?tr.src.rpm
>Caldera: ?.src.rpm
>Conectiva: ?cl.src.rpm
>Engarde: ?.src.rpm
>Immunix: ?_StackGuard.src.rpm
>SuSE: ?.src.rpm
>TurboLinux: ?.src.rpm
>
>Hmmm... actually, looking at that, it's about half split. Well, so
>much for that argument. =)
>
>I'd still say yes, use ?mdk if you're writing the spec for Mandrake.
>If you're trying to make it relatively generic and mean for it to run
>on other distros, don't use the mdk extension.
>
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
