Bug 450040
Summary: | Freedoom 0.6.2 is out | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Xavier Bachelot <xavier> |
Component: | freedoom | Assignee: | Wart <wart> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 10 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-22 22:42:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Xavier Bachelot
2008-06-04 21:49:57 UTC
As a side note, I think this package doesn't need to use a disttag, this is pure datas. Using a dist tag is actually counterproductive, as it forces the duplication of otherwise identical datas to all the releases. Not sure what needs to be done to get the rpms copied from one release to another though. It seems you would need to build the(In reply to comment #1) > As a side note, I think this package doesn't need to use a disttag, this is pure > datas. Using a dist tag is actually counterproductive, as it forces the > duplication of otherwise identical datas to all the releases. Not sure what > needs to be done to get the rpms copied from one release to another though. It seems you would need to build the package for the oldest supported fedora release, then mail rel-eng so they do the needed magic to have the package inherited for all newer releases permanently. (In reply to comment #2) > It seems you would need to build the package for the oldest supported fedora > release, then mail rel-eng so they do the needed magic to have the package > inherited for all newer releases permanently. This is what I've done for other large data packages. But I wonder if it's worth it for freedoom since the package is (only?) 7MB. I usually don't bother with disttagless data packages except for packages > 20MB or more. I know that's a pretty arbitrary cutoff, but in this case the savings would be rather small (7MB per release). Actually, I took this opportunity to learn how the rpm duplication across releases process works. I thought about the size (non-)issue in this case, but was lazy and didn't bother to look. Anyway, as you said, the size limit is arbitrary, and what may be only a little saving for someone might still worth it for another. No strong feeling either way, this was just meant as a note, in case you didn't know about the potential issue and workaround. Regards, Xavier I've built this for rawhide, but I'd like to wait to push it to F-9 and F-8 until this is fixed: http://sourceforge.net/tracker/index.php?func=detail&aid=1939857&group_id=61157&atid=498937 We will need to test this with both prboom and vavoom, as both of these doom engines are in Fedora and depend on prboom. This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping The version of 'rawhide' when this bug was filed is now 'F10'. Thus, the latest version of freedoom is now available in F-10. |