Register buildpack in buildpack registry

[jbyrum]

My name is Jon Byrum and I’m a product manager at Heroku. Your buildpack is one of the top 200 most popular buildpacks on Heroku!

I would like to invite you to publish your buildpack early in our Buildpack Registry, before it is made available to the general public (expected early July).

To register your buildpack, visit: https://addons-next.heroku.com/buildpacks Documentation: https://devcenter.heroku.com/articles/buildpack-registry

Why register?

• By registering early you’ll be able to grab your preferred namespace for the buildpack
• After registering, your buildpack will be available to all Heroku users when they run heroku buildpacks:search. In the future, we will only display registered buildpacks on elements.heroku.com/buildpacks
• The Buildpack Registry makes it easy for you to publish a new version of your buildpack, as well as roll back if there are errors

Recommended naming conventions:

• We recommend that you use the same namespace (e.g., jbyrum) with Buildpack Registry that you use on GitHub
• In general, avoid using "buildpack" in the name of your registered buildpack
  • For example: If your Github repo is github.com/foobar/heroku-buildpack-elixir, then we recommend a name like "foobar/elixir"

It would be greatly appreciated if you could publish before June 18th, as we prepare to make the feature publicly available. Registering a buildpack should take approximately 5 minutes.

If you have any questions about registering (or run into any issues), please email: heroku-buildpack-registry-feedback@salesforce.com

[shunjikonishi]

Hi, Jon. Thanks for invitation.

I'm very surprised that this buildpack is so popular. But unfortunately, I think this buildpack is outdated.

I made this buildpack 4years ago. It uses ffmpeg version 2.x. However current version is 4.x.

This buildpack works if the user satisfied with old ffmpeg. But I don't recommend it. That is the reason I wrote Hacking section in README.(Also that is the reason why this buildpack has so many fork.)

Updating the version of ffmpeg is easy. But I'm not familiar with recent version of ffmpeg.(I'm not using ffmpeg in current job.) So, I don't think to update this buildpack for now.

If you still think this is worth to register, plz let me know.