On 02/02/2011 12:54 PM, ext David Greaves wrote:
On 02/02/11 10:16, Tapio Rantala wrote:
Hi
I saw this from rpmlint:
"W: meego-filelist-empty packages without any files are not allowed in
MeeGo"
>
So, how about meta packages that only exist to provide a name to
require? Are those banned from meego?
And as importantly - does banning them from MeeGo make life difficult
for vendors building on top of MeeGo who may find them useful.
I'd like a way to ensure that packages with no tarball are actually
meta packages and not packaging errors. So can the specfile have
something explicit stating this?
You can always suppress errors reported by rpmlint. I don't know about
the policy regarding those though.
xbmc.rpmlintrc file with something like (guessing here):
addFilter("meego-filelist-empty")
Personally I've put the copyright file into these kinds of packages.
--
Tatu
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
