Comments (6)
https://build.opensuse.org/package/view_file/multimedia:libs/mt32emu/mt32emu-qt.desktop?expand=1
At the moment, my desktop file looks like this.
However, I think the name munt should be dropped in favor of mt32emu and not mention it anywhere except in the description.
from munt.
The hardest part for me, when I create a new package, is to come up with, and even translate into English, Summary and Description for both the main package and all of its subpackages.
I don't think anyone can do it better than the project author.
At the moment it looks like this.
https://build.opensuse.org/package/view_file/multimedia:libs/mt32emu/mt32emu.spec?expand=1
Is there anything you would like to change or add?
from munt.
However, I think the name munt should be dropped in favor of mt32emu and not mention it anywhere except in the description.
Well, it's kind of well-known atm, and probably grouping the subprojects under munt name isn't so bad and should help finding it instead. For instance, MSYS2 also keeps the munt project name as can be seen in their package index.
from munt.
For me, from the point of view of a package maintainer as well as from the point of view of a user of a linux distribution, this is hard to understand.
If a project is called munt, I expect its library to be called libmunt.so.0, its executable (if there is no console utility and only 1 frontend is available), will be called munt, or the console utility will be called munt and the gui munt-qt.
But nothing is called by this name. it's just mentioned and that's it. Everything is named mt32emu and the pure name mt32emu is not used. It is assumed that there will either be a console utility mt32emu in the future or this is the common name of the project.
But the project is called munt and it has a common source code.
I can't get this into my head.
It would be only worse if each component had its own name too.
This also confuses the user. The user knows exactly about munt, he tries to install it sudo zypper in munt
but there is no such package, because it is called mt32emu-qt but the user has no idea about this, he knows only munt.
I don't understand why to get so twisted.
from munt.
Description for both the main package and all of its subpackages.
I don't think anyone can do it better than the project author.
At the moment it looks like this.
https://build.opensuse.org/package/view_file/multimedia:libs/mt32emu/mt32emu.spec?expand=1
Is there anything you would like to change or add?
Well, I've put my version of package descriptions in the packages that already exist :)
You are welcome to look at the rpm packages at SourceForge. Sample descriptions are pulled from the files related to the FreeBSD port included in the source tree (just because it was created first, heh).
There is one thing that looks weird to me in that spec file openSUSE. The library binary and its devel packages require quite some stuff as dependencies. I assume all those aren't really necessary except for building the mt32emu-qt application, so if the user doesn't needs the mt32emu-qt application he could save on installing those dependencies.
from munt.
But nothing is called by this name. it's just mentioned and that's it.
Oh really? We have two projects at GitHub and SourceForge named munt, isn't it enough yet?
Everything is named mt32emu and the pure name mt32emu is not used.
I don't understand this point. mt32emu is the name of the core synthesiser engine, and hence the library that implements this engine. Anyway, both munt and mt32emu names stick for long, they existed when I came to this project, and I'm not going to change this as I personally feel quite comfortable with that. You may simply consider munt to be a codename or something.
It would be only worse if each component had its own name too.
Again, I don't understand this. Each component is supposed to have an unique name, right? Else we would be unable to distinguish them...
This also confuses the user. The user knows exactly about munt, he tries to install it
sudo zypper in munt
but there is no such package, because it is called mt32emu-qt but the user has no idea about this, he knows only munt.
Well, I assume the user would not try to install an unknown package that way. I for one always start with searching, and if doing it right, both "munt" and "mt32emu" should lead the user to the right packages.
I don't understand why to get so twisted.
As I mentioned, this is for historical reasons, and most of the users we have are well aware of the naming.
from munt.
Related Issues (20)
- DOSBox Patch LCD messages to LCDProc
- Problem writing reverb settings over SysEx HOT 3
- Dosbox r4479: MIDI:Can't find device:mt32 HOT 2
- [Feature Request] Partial exhaustion indicator in UI HOT 4
- [UI Feature Request] Numeric entry Output Gain control
- Make UI better self-documenting
- Application crashes occasionally when a new JACK audio device is started
- UI may show obsolete info when a pinned synth is stopped
- Add basic unit tests
- Improve emulation accuracy of partial allocator implemented in old-gen devices
- New Output Gain textboxes don't work well on Windows HOT 1
- Provide callback to inform clients about events of synth engine running out of available partials
- Add visual indication for events when the synth engine exceeds the currently available partials
- is there any documentation on how to use mt32emu? HOT 2
- SHA1 digests in ROMInfo objects may be initialised incorrectly HOT 1
- SteamOS 3.5 - Client 128: 'Munt MT-32' Misssing HOT 5
- Question about using MUNT regarding physical ownership of a tested and working CM-32L unit HOT 12
- [Feature Request] Remember volume or command-line volume option. HOT 1
- More of a question to the creator.
- Guides or information on dumping MT-32 ROM? HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from munt.