ke, 2011-02-02 kello 06:19 -0800, ext Arjan van de Ven kirjoitti: > can you describe what you are trying to do so that maybe we can have > better suggestions?
On some other project derived from meego, create images without a package included in meego package groups. That functionality is provided by alternative package, and you cannot replace original with Provides: for mic. ke, 2011-02-02 kello 10:54 +0000, ext David Greaves kirjoitti: > 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? Actually I don't think that any decent package could be built without tarball accidentally: Source: pointing to something non-existing. %setup fails, and also patches cannot be applied. %build fails. %install fails. %files section cannot be satisfied. > > Should meta packages include copyright/license file to make them > > fit? > The package, however small, has a copyright and license and this > should be provided. Meta package does not have a single line of code. I wouldn't be surprised if somebody wrote letter-to-letter copy of the minimal spec file without looking at the original. With 329 bytes, including all keywords, I don't think that this can be considered much of an "original work". But well, if that's how it is, I'm ok with it. -- Tapio Rantala _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
