| Summary: | mail-mta/postfix-2.3.6 broken URL in pkg_setup | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Wendall Cada <wendallc> |
| Component: | New packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
| Status: | RESOLVED CANTFIX | ||
| Severity: | trivial | CC: | langthang |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Wendall Cada
2007-02-07 20:33:12 UTC
Unfortunately, relevant release notes file is not yet on the filesystem when pkg_setup() is called - which is near the beginning of the emerge process. Looks like we'll have to refer people generically to "read the release notes", leaving it up to them to find the actual release notes, as I couldn't find older 2.3 release notes anywhere on upstream's FTP server. We could refer them to postfix-<latest>.RELEASE_NOTES, but that would mean updating all postfix ebuilds everytime there is a new 2.3 release, which is unthinkable. Any other ideas, anyone? Given that the latest release notes don't apply to older versions, telling people to refer to them to make sure they aren't going to break their mail server would be a bad idea IMHO. I think the best way would be to mirror the (gzipped) release notes on the mirrors infrastructure. We add the release notes to SRC_URI, and have the ebuild download them in pkg_fetch, then just refer the user to /usr/portage/distfiles/postfix-<version>.RELEASE_NOTES.gz When telling them where to read the notes. Because of the special need that this file be accurate. Things can and do seriously break with postfix updates from time to time. I agree fully that this be on the mirrors infrastructure. I think a valid argument can be made for it. And it's quite small. Just my $0.02 Wendall As 2.3.6 is not in the tree anymore, this may be closed I guess. (In reply to comment #4) > As 2.3.6 is not in the tree anymore, this may be closed I guess. > yup |
