> On Mar 3, 2016, at 12:09 AM, Juan Manuel Palacios <j...@macports.org> wrote: >> On Mar 3, 2016, at 3:35 AM, Ryan Schmidt <ryandes...@macports.org> wrote: >>> On Mar 3, 2016, at 00:18, Juan Manuel Palacios <j...@macports.org> wrote: >>> >>> Apache 2 rev-bumped, cf. r146274. >>> >>> On a side note, and if I may in this same thread, do we have any policy for >>> not moving the Apache 2.4 port out of “dev”? Not too sure when it became >>> the recommended release series by the ASF, but it certainly isn’t dev any >>> longer. >> >> There's a ticket you can read. We can't just replace the current apache2 >> port with the current apache24-devel port because it also changes the >> directory layout.
> > Yeah, that I understand, we keep versioned ports for other packages too, e.g. > mysql55, mysql56, mysql57, and other examples. And we don’t replace one with > the other for a myriad of reasons. With versioned apache24 modules like apache24-mod_python27. > So we could deprecate the apache24-devel port and create apache24, maybe even > also deprecating apache2 and eventually replacing it with apache22, which > needless to say would be compatible with the former, and would live on in > parallel to apache24, just as mysql55 does to mysql56, etc. > > You have a URL for that ticket that you mention? https://trac.macports.org/ticket/35824 — Brad _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
