Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix multiarch support on Debian/Ubuntu #4

Merged
merged 1 commit into from Aug 4, 2012

Conversation

noirbizarre
Copy link
Contributor

Allow installation from pip/easy_install on multiarch enabled distrib.

See https://wiki.ubuntu.com/MultiarchSpec

I think there some fix to apply to mapnik-utils too.

Backporting to 2.0.x to have it in pypi would be very nice!

kiorky added a commit that referenced this pull request Aug 4, 2012
Fix multiarch support on Debian/Ubuntu
@kiorky kiorky merged commit b5d1a5b into mapnik:master Aug 4, 2012
@kiorky
Copy link
Contributor

kiorky commented Aug 4, 2012

Thx !

@kiorky
Copy link
Contributor

kiorky commented Aug 4, 2012

@kiorky
Copy link
Contributor

kiorky commented Aug 4, 2012

I can also make you co maintainer of pypi, just give me your id.
Just use zest.releaser's fullrelease (see buildout) to make a proper release.

@noirbizarre
Copy link
Contributor Author

Glad to help!!
Here's my pypi ID: noirbizarre (same as github)

I don't much about zest-releaser but it seems interesting.
I going learn about it right now!

Thanks!

@kiorky
Copy link
Contributor

kiorky commented Aug 5, 2012

added to pypi as maintainer

basically:

  • have the buildout running
  • easy_install -U setuptools_git (you need it both in your buildout scripts & in your python because zest.releaser calls directly python under the hood)
  • then when you release, commits what it needs to, but dont increment any version stuff nor update the date in CHANGES because it is handled by zest.releaser
  • finally use the magical bin/fullrelease, answer the questions are you are done.
    • tag creation, version increment, date update, pypi & github checkins will be handled for you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants