[maemo-developers] [maemo-developers] docpurge in maemo 2.1
From: Marius Vollmer marius.vollmer at nokia.comDate: Wed Dec 13 14:33:28 EET 2006
- Previous message: [maemo-developers] docpurge in maemo 2.1
- Next message: [maemo-developers] docpurge in maemo 2.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"ext Miko Nieminen" <miko.nieminen at gmail.com> writes: >> - Why is docpurge executed when installing packages in scratchbox >> environment in the first place? You don't really need (or want) to >> remove documentation there. > > I agree it is not needed, but osso-ai metapackage depends on it and that > is the reason why it's in there, I suppose. Actually I think it's wrong > that osso-ai depends on docpurge, maybe it should rather suggest or > recommend it? osso-ai is a meta package that should only be used when creating product flash images. It should not be in the SDK. >> docpurge comes in the maemo 2.1 rootstraps, both i386 and armel. >> In the sardine build robot I work around this by deleting >> docpurge. It would be good to have this fixed. >> > > IMHO, existence of docpurge is just a way to make a quick fix for poor > packaging. Well. :) Docpurge is a hack and should go away, agreed, but it's not entirely obvious what it should be replaced with. I think our best option is a combined approach of having dpkg filter certain files during installation, and splitting documentation out of arch packages if that makes sense. Whether splitting a package makes sense depends on how much we want to deviate from upstream if upstream doesn't want to follow us.
- Previous message: [maemo-developers] docpurge in maemo 2.1
- Next message: [maemo-developers] docpurge in maemo 2.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]