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

Rename the AppImage production tool #86

Open
probonopd opened this issue Oct 24, 2020 · 8 comments
Open

Rename the AppImage production tool #86

probonopd opened this issue Oct 24, 2020 · 8 comments

Comments

@probonopd
Copy link
Owner

probonopd commented Oct 24, 2020

go-appimage currently consists of two tools, one to produce AppImages and one to consume AppImages.

They share a lot of code and are intended to work well together, and be developed in sync with each other in the same repository.

However, the current naming is confusing, since there is an earlier low-level tool with the name appimagetool that has only one functionality (turns AppDir into AppImage), whereas the tool to produce AppImages in this directory:

  • Deploys dependencies into an AppDir, including special cases such as Qt, GStreamer, etc.
  • Turns AppDir into AppImage
  • Automatically creates update information
  • Signs AppImage
  • Creates zsync file
  • Uploads AppImage and zsync file
  • Publishes the AppImage via a publish/subscribe mechanism (currently, MQTT) to which the AppImage consumption tool (currently, appimaged in this repository) and application catalogs such as appimage.github.io may subscribe (work in progress; implementation is not final yet)
  • ...

in a way as automated and with as little configurability as possible.

It will be the only AppImage creation tool that I have bandwidth to support. All others will be community-based and supported by their respective authors.

The current name (appimagetool) is not fitting.

Hence, we need to

  • Find a better name
  • Rename the tool

Ideas -- your ideas are welcome

  • appimageproductiontool
  • appimageproduce
  • autoappimage
  • appimagegenerate
  • appimagefoo

cc @srevinsaju @TheAssassin

@srevinsaju
Copy link
Contributor

autoappimage looks like a good option to me, as it conveys most of the stuff are automated.

@probonopd
Copy link
Owner Author

probonopd commented Oct 24, 2020

  • autoappimagetool

Better ideas, anyone? ;-)

@mihaiav
Copy link

mihaiav commented Nov 13, 2020

  • appimage-mk
  • appimagemk

@srevinsaju
Copy link
Contributor

  • mkappimage

@RazZziel
Copy link

AppImageStudio?

I don't dislike appimagetool though, all those new features still fit in this "AppImage power tool" concept
This project feels like a reimplementation of the same tool with additional features, rather than a new tool, so a major version change kinda makes more sense than a name change to me

@probonopd
Copy link
Owner Author

probonopd commented May 6, 2022

Possibly

  • low level tool: appimagedeploy: It deploys apps as AppImages
  • low level tool: appdir2appimage: It turns existing AppDirs into AppImages

@probonopd probonopd pinned this issue May 6, 2022
@zevlee
Copy link

zevlee commented Apr 7, 2023

Have you considered simply appimager?

@ilaicraftYT
Copy link

genappimage

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

No branches or pull requests

6 participants