#15135: variant +sidebar of port mutt-devel fails patch phase ------------------------------------------+--------------------------------- Reporter: shreevatsa.public@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: mutt, mutt-devel, patch ------------------------------------------+--------------------------------- Comment (by shreevatsa.public@gmail.com): Yeah, mutt-devel +sidebar works fine by itself. I guess one of the others was conflicting. Fixing this probably requires changing the way the patch phase works -- is it possible to do it so that there are no conflicts? Would tools like quilt help? [Can I change the component of this ticket to MacPorts Base bugs?] -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/15135#comment:1> MacPorts </projects/macports> Ports system for Mac OS

#15135: variant +sidebar of port mutt-devel fails patch phase ------------------------------------------+--------------------------------- Reporter: shreevatsa.public@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: mutt, mutt-devel, patch ------------------------------------------+--------------------------------- Comment (by shreevatsa.public@gmail.com): Well, I thought there must exist some tools that keep track of patches a bit more smartly, and decrease the need for manual resolution. I vaguely remember seeing that quilt can do something in this direction (I think it lets one specify the order in which patches should be applied). [Offtopic: I don't really know what would be a good way to solve this, since variants introduce a combinatorial explosion that makes it hard to test all cases. mutt-devel has 21 variants, which means there are more than *two million* ways of installing it. This is terrible, especially for a port that has no maintainers. Many of those variants could simply be turned on... I think variants of the form "--enable-feature" should be generally encouraged to not be variants at all, when they do not cause any undesirable consequences.] -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/15135#comment:3> MacPorts </projects/macports> Ports system for Mac OS

#15135: variant +sidebar of port mutt-devel fails patch phase ------------------------------------------+--------------------------------- Reporter: shreevatsa.public@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: closed Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: fixed | Keywords: mutt, mutt-devel, patch ------------------------------------------+--------------------------------- Changes (by jmr@macports.org): * status: new => closed * resolution: => fixed Comment: I marked those variants as conflicting in r36310, which is all we can really do. Quilt is a very handy tool, but it's for keeping track of patch series, where each patch applies to the result of the last. It doesn't resolve the conflicts for you, it just makes it easy to update the patches after they are resolved. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/15135#comment:5> MacPorts </projects/macports> Ports system for Mac OS