Hi,
Looking at the packaging conventions, I didn't see any information for creating devel packages, which is something rather... common :-) (or maybe I missed the page about this)
It looks to me like all packages use different conventions for this, while a standard pattern for summary and description would make sense.
Eg, a standard summary could be "Development files and libraries for $package" and a standard description could be "Headers and libraries for developing applications that use $something."
Also, right now, it's not clear to me if the group of the devel package should be the same as the non-devel package or something like Development/Libraries.
Any opinion?
Thanks,
Vincent
On Thu, Oct 23, Vincent Untz wrote:
Hi,
Looking at the packaging conventions, I didn't see any information for creating devel packages, which is something rather... common :-) (or maybe I missed the page about this)
It looks to me like all packages use different conventions for this, while a standard pattern for summary and description would make sense.
Eg, a standard summary could be "Development files and libraries for $package" and a standard description could be "Headers and libraries for developing applications that use $something."
We had that in the past, but it didn't worked out. There were too many exceptions necessary. But I don't remember details anymore.
Also, right now, it's not clear to me if the group of the devel package should be the same as the non-devel package or something like Development/Libraries.
Should be somewhere below Development, not in the same RPM group as the main package is.
On Thursday 23 October 2008, Vincent Untz wrote:
Also, right now, it's not clear to me if the group of the devel package should be the same as the non-devel package or something like Development/Libraries.
it should be under Development/. There is even a rpmlint check for that.
Not that it would matter, since we don't use/show rpm groups anymore. Thats why I want to remove the rpmlint warning again.
Greetings, Dirk
On Tue, 11 Nov 2008 20:36:23 +0100, you wrote:
Not that it would matter, since we don't use/show rpm groups anymore.
Care to explain why that is so?
Philipp
Philipp Thomas escribió:
Care to explain why that is so?
Obsoleted by "patterns" I guess.. and waay more useful ;-)
Cristian Rodríguez schrieb:
Philipp Thomas escribió:
Care to explain why that is so?
Obsoleted by "patterns" I guess.. and waay more useful ;-)
Patterns are useful but I liked the RPM group view in YaST and really miss it. Don 't understand why it was dropped since it shouldn't create much hassle to support it.
Wolfgang
* Dirk Müller [2008-11-11 20:36]:
Not that it would matter, since we don't use/show rpm groups anymore.
My "rpm -qi" still shows it.
Regards, Bernhard