openpkg
/
openpkg-packages
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
536 Commits
1 Branch
2 Tags
594 MiB
Tree: 7d6a9a204d
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7d6a9a204d'
${ noResults }
Commit Graph

13 Commits (7d6a9a204dd1e13a48af68543998cc7d9567b38e)

Author SHA1 Message Date
Dr. Ralf S. Engelschall 50cd7b937e upgrade to Python 2.2
24 years ago
Dr. Ralf S. Engelschall 5cc2b7f1fd upgrade to 2.2c1
24 years ago
Dr. Ralf S. Engelschall 8cdd11b95c remove trailing zero to conform with new scheme
24 years ago
Dr. Ralf S. Engelschall 139dc60d0a adjust distribution and release
24 years ago
Dr. Ralf S. Engelschall db8c270d2d Bump releases.
24 years ago
Dr. Ralf S. Engelschall 75ec335002 add OpenPKG to copyright lines
24 years ago
Dr. Ralf S. Engelschall 2171079274 Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled.
24 years ago
Dr. Ralf S. Engelschall 392c380282 upgrade to Python 2.2b2
24 years ago
Dr. Ralf S. Engelschall 92722d47de bump to the correct 0.9-20011025.0
25 years ago
Dr. Ralf S. Engelschall 2c1ab0fbe0 upgrade dependencies because of l_branch usage
25 years ago
Dr. Ralf S. Engelschall 6d5f952f16 Switch to using "YYYYMMDD.X" as Release for -CURRENT packages.
25 years ago
Dr. Ralf S. Engelschall a1cc16b06c braindead Python insists on using 'python2.2' as the directory names
25 years ago
Dr. Ralf S. Engelschall f22dc2cab9 New package: Python 2.2b1
25 years ago