[RFC] Apache-related ports changes
sheepkiller at cultdeadsheep.org
Thu Jan 15 08:11:37 PST 2004
On Thu, 15 Jan 2004 16:00:16 +0100
dirk.meyer at dinoex.sub.org (Dirk Meyer) wrote:
> This wwill add more work for each port,
> as with updates teh port may no longer work for ap13-
> or is now supporting ap2- and more ....
> To make a prot reflect this, we have to rename it in furture.
> CVS reprocopy would be needed for each version we addionally support.
> I would like to avoid that, as this breaks updating for the ussers.
> What about "russian/apache13" ?
> and another API "www/apache13-modsssl" won't fit in this prefix idea
> Better we use a suffix in pkg_name or leave is as it is.
> We can easy make a slave port so we can have packages for more than
> one apache port.
It's a dilemna, that's why I asked for comment.
Slave ports is a nice idea, and we can auttomacily add a correct
We gonna take as example mod_security. As many people are currently
switching to apache2, we can provide mod_security packages for apache13
and apache2 (and surely apache21). If you follow currently bad habit,
we'll name the slave port mod_security2.
If mod_security team releases a "new technology" version, it will be
mod_security 2.0. As someone will port it, how will he call the
Anyone who browse ports collection will say "hey man, what a mess !"
We can keep actual "anarchy", but I doubt we can keep it homogeneous
> > - apache version/port detection
> It must be possible to build a package in jail,
> with correct dependencies, even if no ports installed.
> autodetection can help, but options to force a customized build
> are more important!
In fact apache will be split in 3 major branches, containing ports.
Autodetection will first check the branch, and then the ports.
For apache13, it will detect their variants, and for apache2 variants
(currently not applicable) and MPMs.
User can still define APACHE_PORT=<what you want> if no port is currently
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040115/d081301c/attachment.bin
More information about the freebsd-ports