Changes between Initial Version and Version 1 of Ticket #70, comment 4


Ignore:
Timestamp:
Mar 22, 2014, 2:13:28 PM (11 years ago)
Author:
dmik

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #70, comment 4

    initial v1  
    55Regarding further builds of Python. This relates not only to 2.x but to 3.x as well of course as 3.x is still derived from 2.x I guess (and hence most our patches from this SVN will be still applicable).
    66
    7 Forgot to mention that I also dropped your patches where you hardcode your specific paths (like `/extras/include`) and build options. Options and paths are specified at the RPM .spec level here (which acts much like a build script that everybody may use even if they don't actually want to provide an RPM), so they should not be hardcoded in SVN. If you still want to have them, we may simply create a branch named `psmedley` here and you can keep all your patches there. I can also help you with this branch. And we may give you commit access I'm sure (so that you could work on youк branch on your own) - this would be even better than attaching patches to tickets..
     7Forgot to mention that I also dropped your patches where you hardcode your specific paths (like `/extras/include`) and build options. Options and paths are specified at the RPM .spec level here (which acts much like a build script that everybody may use even if they don't actually want to provide an RPM), so they should not be hardcoded in SVN. If you still want to have them, we may simply create a branch named `psmedley` here and you can keep all your patches there. I can also help you with this branch. And we may give you commit access I'm sure (so that you could work on your branch on your own) - this would be even better than attaching patches to tickets..