-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
feature request: combine this and the graphicsmagick buildpacks #7
Comments
This is an awesome idea! Can you submit a pull-request against the graphcis-magick one? We can rebrand as 'heroku-magick-buildpack' and combine both of them. If you want, I can give you commit access! |
i tried using it, but it didn't even build (i forgot which package failed, i think libpng). i updated the package versions manually since i guess the server you download the source code from deletes all old versions (very annoying! but i can't find any other servers). since i don't know shell very well, do you mind just double checking your packages work and updating them? after that i'll try hacking this again. i'm on os x; i'm not sure what you're using. |
The build are done directly on Heroku through Vulcan, so it is not bound to a platform. I think I'll have some time next week: I'll work on the graphicsmagick package, as it is more up-to-date. |
Fix PATH in profile.d
i noticed that the graphicsmagick buildpack is more up to date than this package. why not just combined these two buildpacks into a single buildpack that has both packages and other packages like libpng and zlib? the overhead wouldn't be much, and it'll be easier to maintain.
another option is just to have one be the fork of the other.
The text was updated successfully, but these errors were encountered: