Hans de Goede wrote: > > Michael Thomas wrote: >> At the last FESCo meeting the following packaging guideline was modified: >> >> * Game music or audio content is permissible, as long as the content is >> freely distributable without restriction, and the format is not patent >> encumbered. >> >> The restriction on ogg files was removed, but it's still not allowed to >> ship mp3 files for game music. >> >> This clarifies the rule for game music files, so it's clear now that >> packages like >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190267 are ok. >> >> However, brought up a concern about the disk usage from having duplicate >> packages of this static content on the fedora mirrors. Clearly most >> game data/music should be in a noarch package, but it still means that >> each dist (fc4, fc5, fc6...) will end up with a duplicate package. >> >> The recommendation to work around this is to _not_ use the %dist tag on >> large, noarch, game data packages. This will result in identical >> package filenames when built on each of the branches. While this won't >> immediately reduce the disk usage on the mirrors, it will be one step >> forward to helping solve the problem. >> >> Does anyone else see any problem with prohibiting the %dist tag for game >> data packages (unless the packager has a reasonable justification)? >> >> --Wart >> > > Erm, will this work? This means one can only do "make tag" for one > branch won't plague be upset when you tell it to make something on FC-5 > and the passed tag belongs to the devel branch? > I think we need to think this one over a bit more. For now I'm just going along with raidem-music with %{?dist}, I want to get that of my todo list. Then we can take our time to come up with something sane for this. We might as well include packages in the discussion were upstream doesn't split content and engine and we want to split these. Regards, Hans
