Jim Fulton wrote:
Tim Peters wrote:
[John Belmonte]
I'm trying to update my experimental ZODB Debian package to 3.4.0a1. The
new change of having version numbers hard-coded in file paths within the
source package (e.g. Dependencies/BTrees-ZODB3-3.4.0a1) is very
troubling.
Not really new: for ZODB
Tim Peters wrote:
[John Belmonte]
I'm trying to update my experimental ZODB Debian package to 3.4.0a1. The
new change of having version numbers hard-coded in file paths within the
source package (e.g. Dependencies/BTrees-ZODB3-3.4.0a1) is very
troubling.
Not really new: for ZODB it started with 3
[John Belmonte]
> I'm trying to update my experimental ZODB Debian package to 3.4.0a1. The
> new change of having version numbers hard-coded in file paths within the
> source package (e.g. Dependencies/BTrees-ZODB3-3.4.0a1) is very
> troubling.
Not really new: for ZODB it started with 3.3b1, last
I'm trying to update my experimental ZODB Debian package to 3.4.0a1.
The new change of having version numbers hard-coded in file paths within
the source package (e.g. Dependencies/BTrees-ZODB3-3.4.0a1) is very
troubling. This means that any patch to the upstream source I try to
maintain will s