Opened 8 years ago

Last modified 7 years ago

#34130 new enhancement

subversion: mod_dav_svn subport

Reported by: ryandesign (Ryan Schmidt) Owned by: danielluke (Daniel J. Luke)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: blair (Blair Zajac), larryv (Lawrence Velázquez), nonstop.server@…, cooljeanius (Eric Gallager)
Port: subversion, mod_dav_svn

Description

Could mod_dav_svn be changed from a variant to a subport?

Change History (11)

comment:1 Changed 8 years ago by danielluke (Daniel J. Luke)

really, all of the bindings ports should also be moved to subports.

As far as I know, nothing depends on mod_dav_svn (which is why it was never moved into its own port), it saves some time (when building) if everything is built at once (which is why the bindings ports used to be variants).

comment:2 Changed 8 years ago by ryandesign (Ryan Schmidt)

But what many a user will do is

  1. install subversion with default variants
  2. realize some time later that they want mod_dav_svn
  3. maybe do "port search mod_dav_svn" and not get any results and be confused
  4. maybe realize it's a variant of Subversion and reinstall subversion with +mod_dav_svn, having to rebuild everything

We're talking on the mailing list about upgrading apache2 to version 2.4 eventually, which will necessitate increasing the revision of all Apache module ports to force them to rebuild with the new ABI. I'd like at that point to be able to increase the revision of only the mod_dav_svn subport and not have to force a rebuild on everybody not using mod_dav_svn.

comment:3 in reply to:  2 Changed 8 years ago by danielluke (Daniel J. Luke)

Replying to ryandesign@…:

I'd like at that point to be able to increase the revision of only the mod_dav_svn subport and not have to force a rebuild on everybody not using mod_dav_svn.

If we're going to do it smoothly for end-users it's going to require a rebuild of everyone anyway (since we'll want a rev bump of subversion with +mod_dav_svn depending on the new subport), right?

comment:4 Changed 8 years ago by ryandesign (Ryan Schmidt)

Or the move of mod_dav_svn to a subport could be combined with upgrading the subversion port to 1.7.5, whenever that gets released.

comment:5 Changed 8 years ago by ryandesign (Ryan Schmidt)

By the way it won't be possible for the +mod_dav_svn variant to declare a dependency on the new mod_dav_svn subport because the new mod_dav_svn subport will have a dependency on the subversion port so that would be a circular dependency. Instead, you'll probably just want the old +mod_dav_svn variant to display an error message advising the user what to do. That's how I handled turning variants into (sub)ports in php5 a year or two ago.

comment:6 Changed 8 years ago by blair (Blair Zajac)

The changes for Apache 2.4 support are currently in a vetoed state: http://svn.apache.org/viewvc?view=revision&revision=1303348

comment:7 in reply to:  6 Changed 8 years ago by blair (Blair Zajac)

Replying to blair@…:

The changes for Apache 2.4 support are currently in a vetoed state: http://svn.apache.org/viewvc?view=revision&revision=1303348

And those issues have been resolved and are awaiting votes and a merge into the 1.7.x branch:

comment:8 Changed 8 years ago by danielluke (Daniel J. Luke)

Owner: changed from dluke@… to dluke@…

comment:9 Changed 7 years ago by larryv (Lawrence Velázquez)

Cc: larryv@… added

Cc Me!

comment:10 Changed 7 years ago by nonstop.server@…

Cc: nonstop.server@… added

Cc Me!

comment:11 Changed 7 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

Note: See TracTickets for help on using tickets.