Re: Fuppes: Package Names and the Separation of a Project into Packages
On Sat, Dec 19, 2009 at 11:31:50PM +1100, Robert Massaioli wrote:
> $ ls *.deb -1
> fuppes_0.654-1_i386.deb
> fuppes-core-plugin-presentation_0.654-1_i386.deb
> fuppes-database-plugin-mysql_0.654-1_i386.deb
> fuppes-database-plugin-sqlite3_0.654-1_i386.deb
> fuppes-decoder-plugin-flac_0.654-1_i386.deb
> fuppes-dev_0.654-1_all.deb
> fuppes-encoder-plugin-twolame_0.654-1_i386.deb
> fuppes-metadata-plugin-dlna_0.654-1_i386.deb
> fuppes-metadata-plugin-exiv2_0.654-1_i386.deb
> fuppes-metadata-plugin-libavformat_0.654-1_i386.deb
> fuppes-metadata-plugin-libmp4v2_0.654-1_i386.deb
> fuppes-metadata-plugin-magick_0.654-1_i386.deb
> fuppes-metadata-plugin-taglib_0.654-1_i386.deb
> fuppes-transcode-plugin-ffmpeg_0.654-1_i386.deb
> fuppes-transcode-plugin-magick_0.654-1_i386.deb
> libfuppes0_0.654-1_i386.deb
> $
>
> I look at the sheer number of packages there and think that, although it
> provides alot of freedom as to what you install on your machine, it might be
> too fine grained; maybe we need less packages and every package installs
> more (or even a single package with everything)? But I'm not sure and that
> is why I am asking here.
>
> What should we do in this case? Should I try and get all of those packages
> into debian or should I group them into larger but fewer packages?
Hm I'd first consider the size of each of the plugin packages. If
they're relatively small you could consider grouping them, seems like
that it is already somewhat done in core, database, encoder, metadata,
... if these are not depending on each other it could be a sensible
choice. If they're really small all in one is ok as well.
Regards
Christoph
--
/"\ ASCII Ribbon : GPG-Key ID: 0xD49AE731
\ / Campaign : CaCert Assurer
X against HTML : Debian Maintainer
/ \ in eMails : http://www.debian.org/
http://www.christoph-egger.org/
Reply to: