Revision history [back]

You really shouldn't try to edit existing debs. You'll confuse anyone who's expecting to have the upstream version, and your changes may be overwritten by an update if the package maintainer releases a new version.

There are a few things that you can try:

• If you have bugfixes or new features in the upstream package, submit them as a pull request. They'll benefit the rest of the community, in addition to your colleagues.
• If you're just adding configuration files or launch scripts that don't have to be part of the upstream package, consider creating your own package. You can then distribute or release your package as you see fit.

You really shouldn't try to edit existing debs. You'll confuse anyone who's expecting to have the upstream version, and your changes may be overwritten by an update if the package maintainer releases a new version.

There are a few things that you can try:

• If you have bugfixes or new features in the upstream package, submit them as a pull request. They'll benefit the rest of the community, in addition to your colleagues.
• If you're just adding configuration files or launch scripts that don't have to be part of the upstream package, consider creating your own package. You can then distribute or release your package as you see fit.