[...]



Always BuildRequires: <thing>-devel forms only, not lib<thing>-devel.



stefan> Sure, but:

ok, will fix in teh same batch.

/me decides to spend the rest of the evening recompiling all his
packages.

Just wondering, is there going to be a scheme to retire some of the Obseletes / Provides pairs that are floating arround. Some packages are packed with them, perhaps some system / procedure can be throught of to manage this. Or to give a sign when some of them can be removed.

/me thinks that this is optimist.

:-)

stefan> $ urpmq attr-devel
stefan> no package named attr-devel

stefan> $ urpmq dm-devel
stefan> no package named dm-devel

stefan> $ urpmq ext2fs-devel
stefan> no package named ext2fs-devel

stefan> $ urpmq xfs-devel
stefan> no package named xfs-devel

stefan> I understand where this is coming from, and I agree that it needs to
stefan> be done. But I don't think that it needs to be brought up in this
stefan> discussion. I'm getting the feeling that somebody is looking for
stefan> something to pick on...

stefan> I suggest:

stefan> *  rpmlint is adjusted to warn about (& enforce?) this on uploads;
stefan> * a document is written describing these changes so this can be
stefan> finalized into some sort of  guideline / policy. So people can
stefan> read it through, understand how it works and how it should be
stefan> implemented in the packages;


There is a document:

http://people.mandrakesoft.com/~gc/<somewhere>

Did you look in the TeamRoom(tm) yet?

stefan> For instance: I don't understand how the mklib stuff works and how I
stefan> should fix the rpmlint errors I get on the topic.

Just fixed it for dmapi, it is trivial:

%define lib_name_orig %mklibname dm

instead of

%define lib_name_orig libdm

OK... This explains how it was done for this package. I guess this can be applied to any package complaining about missing mklib?

Rule of thumb:
- when you have a problem of that kind, look for a package maintained
 by gb about how it is done there :p

uhm... you are kidding, right?

We need to do better than this... at least write a page on the wiki about it... or make a link on the wiki to where the document is.

regards,

Stefan

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Reply via email to