Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Feb 2016 17:40:49 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 205852] Be nicer about multiple sqlalchemy ports
Message-ID:  <bug-205852-21822-fqvw4kqekt@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205852-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-205852-21822@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205852

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |koobs@FreeBSD.org,
                   |                            |python@FreeBSD.org,
                   |                            |robak@freebsd.org
           Keywords|                            |needs-qa

--- Comment #17 from Kubilay Kocak <koobs@FreeBSD.org> ---
(In reply to Palle Girgensohn from comment #15)

I don't believe that's feasible.

The reason why multiple versions exist because API compatibility changes
between minor versions (perfectly ok), and consuming packages lag behind the
latest major.minor until they have a chance to update.

The pattern of creating a new fooXY and leaving dependent ports on their ol=
der
versions is because correctly, accurately and completely testing for not ju=
st
build time fixes, but correct runtime function (and/or regressions) is not
something a sweeping change can achieve, and is best left to individual
maintainers.

Yes, maintainers should be encouraged to update the dependencies.
Yes, if older versions are no longer supported, they should be DEPRECATED.=
=20
Yes, if port upstreams have 'bumped' their sqlalchemy dependencies, the por=
ts
should follow suite.

See Also:

Upgrade databases/py-sqlalchemy
https://reviews.freebsd.org/D908

Which is still open (CC'ing bartek@)

This is a very similar problem space to our djangoXY ports, and deserves
careful consideration.

Also why is this a Ports Framework issue, when the changes are for two
individual ports?=20

I believe this needs python@ too, and it would be beneficial if any solution
applied to other instances where multiple fooXY and multiple consumers for =
said
ports exist, with ranged or limited dependency specifications.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205852-21822-fqvw4kqekt>