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 binary fvwm3 -> fvwm #440

Closed
slazav opened this issue Feb 22, 2021 · 2 comments
Closed

rename binary fvwm3 -> fvwm #440

slazav opened this issue Feb 22, 2021 · 2 comments
Labels
type:bug Something's broken!

Comments

@slazav
Copy link
Contributor

slazav commented Feb 22, 2021

If one wants to make fvwm3 package, there are two good choices:

  • it replaces old fvwm
  • it can be installed together with old fvwm

In the first case it's good to rename fvwm3 binary+manpage to fvwm. In the second case something should be done with other file conflicts (module manpages, fvwm-config/fvwm-root programs). I think replacing of fvwm2 should be done here.

@slazav slazav added the type:bug Something's broken! label Feb 22, 2021
@ThomasAdam
Copy link
Member

Hi @slazav

Possibly in the future. For now, there are the --program-prefix, --program-suffix, and --program-transform-name options to ./configure which you can use to help with this.

But I won't be doing anything about any of this just yet -- this would be a wider change than just the fvwm3 binary name. Now is not the time.

@slazav
Copy link
Contributor Author

slazav commented Feb 22, 2021

It's certainly not a big problem, it's easy to rename files when making the package. I just wanted to say about this choice. It always happens when you start thinking how to install fvwm3 in your system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something's broken!
Projects
None yet
Development

No branches or pull requests

2 participants