| 1 |
On Fri, 29 Aug 2014 10:08:04 -0700 |
| 2 |
Brian Dolbec <dolsen@g.o> wrote: |
| 3 |
|
| 4 |
> |
| 5 |
> |
| 6 |
> I have changed the version to 9999 and rebased your new-install branch |
| 7 |
> on currrent master, and pushed it to my github account. |
| 8 |
> |
| 9 |
> https://github.com/dol-sen/portage |
| 10 |
> |
| 11 |
> I also am attaching the ebuilds I edited slightly |
| 12 |
> |
| 13 |
> I have uploaded the 2.2.13_pre1 and _pre2 tarballs to my dev space. |
| 14 |
> _pre2 differs from _pre1 in that _pre2 is with the rebased git |
| 15 |
> sources, while _pre1 is Michal's original branch code. |
| 16 |
> |
| 17 |
> you can rename the _pre2.ebuild to _pre1.ebuild to test at your |
| 18 |
> pleasure. |
| 19 |
> |
| 20 |
|
| 21 |
|
| 22 |
OK, all previous problems I reported with setup.py were due to my |
| 23 |
checkout having some stale files or something sdist didn't like. Even |
| 24 |
though an updated mkrelease.sh worked on the same files. The doc, |
| 25 |
epydoc failure was due to my tree being a little too old, it was |
| 26 |
missing an update to the distutils-r1.eclass mgorny did. |
| 27 |
|
| 28 |
As for the version updating. I have removed it from the ebuild I have. |
| 29 |
There were too many places that updated the version, the ebuild code |
| 30 |
was missing the setup.py sed for it to be consistent. Also the ebuild |
| 31 |
should not have to. I think that was from a time when portage releases |
| 32 |
were just patches to previous tarballs. |
| 33 |
|
| 34 |
Thanks to Michal for helping me figure out the errors he was unable to |
| 35 |
reproduce. |
| 36 |
|
| 37 |
I've uploaded a 2.2.13_pre4.tar.bz2 tarball to my releases/portage dir. |
| 38 |
I've also attached the latest _pre4 ebuild. |
| 39 |
-- |
| 40 |
Brian Dolbec <dolsen> |
Archives