1 |
Since the mid 15.x.x releases of twisted, upstream changed from the |
2 |
split releases twisted-{core,names,web,...} to a single twisted package |
3 |
release. Our gentoo tree has been behind with upstream releases since |
4 |
then partially due to this change and the work involved in the |
5 |
conversion. |
6 |
|
7 |
I am pleased to inform you that I have now completed the new twisted |
8 |
package ebuilds and updated/additional/new dependencies. There are now |
9 |
dev-python/twisted-16.2.0 and 16.3.2 releases in the gentoo tree and I |
10 |
am working on 16.4.1 to get the tests working before adding it to the |
11 |
tree. I have been doing testing of the 16.2 and 16.3 releases in my |
12 |
buildbot-0.9.0 (day job) work without any issues. |
13 |
|
14 |
Currently I have added dev-util/buildbot, dev-util/buildbot-worker, |
15 |
www-servers/tornado, dev-python/autobahn, dev-python/txrequests |
16 |
ebuilds which have ||() dependencies on either the old split twisted |
17 |
or new twisted single pkg dependencies. |
18 |
|
19 |
Since there are no longer any split twisted-* pkg releases, any new |
20 |
pkgs/ebuilds should be made with either the new dev-python/twisted only |
21 |
or ||() twisted pkgs dependencies as the maintainer sees fit. You |
22 |
should also list the new dev-python/twisted pkg first in any ||() deps |
23 |
you add. I have come across a portage bug where the resolver was not |
24 |
able to solve a conflict between the old split pkgs and the new single |
25 |
pkg where it should have been able to. This was partially due to having |
26 |
the old split twisted pkgs listed as the first (left) entry in the ||(). |
27 |
|
28 |
You should not introduce new pkgs and hopefully new ebuild versions of |
29 |
existing pkgs that list only the old split twisted pkgs as dependencies. |
30 |
I am sure that eventually the old split releases will be tree-cleaned |
31 |
at some future point. |
32 |
|
33 |
Thank you |
34 |
-- |
35 |
Brian Dolbec <dolsen> |