Was reminded of a conversation @GMaq and myself were having where he was unable to build Seq66 so I decided to do an exercise tonight and built my first deb file.
I copied the dependencies bit on the control file from an deb file of an old version hosted on the opensuse build site. Any feedback would be appreciated
I inserted a deb file into the deb file which when installed placed it in the root folder. Uninstalling removes it or can remove the file individually with a delete command.
I inserted a deb file into the deb file which when installed placed it in the root folder. Uninstalling removes it or can remove the file individually with a delete command.
Hi, thanks very much for taking time to do that!
I noticed the original error but hadn't tracked it down yet and you already fixed it! It installs and runs well here on AVL 23 (unsurprisingly since you built it on MX-23).. I would add a menu Icon etc. if you want one I can come up with something unless you're into graphic art yourself.
i understand that this is a ad hoc proof of concept attempt, but there is nothing to rate for me without the source code of the packaging (the debian folder) available.
I inserted a deb file into the deb file which when installed placed it in the root folder. Uninstalling removes it or can remove the file individually with a delete command.
Hi, thanks very much for taking time to do that!
I noticed the original error but hadn't tracked it down yet and you already fixed it! It installs and runs well here on AVL 23 (unsurprisingly since you built it on MX-23).. I would add a menu Icon etc. if you want one I can come up with something unless you're into graphic art yourself.
There should be icons in /usr/local/share/pixmap /usr/local/share/seq-0.99/icons and /usr/local/share/seq-0.99/pixmaps. The xfce whisker menu uses one from the first. Maybe enlightenment uses a folder not mentioned?
i understand that this is a ad hoc proof of concept attempt, but there is nothing to rate for me without the source code of the packaging (the debian folder) available.
I just have a control file in this folder with the following text.
Package: seq66
Version: 0.99.14
Maintainer: Chris Ahlstrom <ahlstromcj@gmail.com>
Description: Native JACK/ALSA MIDI live sequencer refactored from seq24 and sequencer64.
Seq66 provides major upgrades to seq24: C++14 support, support for
native JACK MIDI, SMF 0 files, a range of PPQN values, more MIDI controls,
more scales, chord-generation, expanded configuration options, pause,
event-editing window, tap-tempo, more keystroke control, and many other
enhancements and fixes. A Qt-5-based application, it also builds on that
other operating system.
Homepage: https://github.com/ahlstromcj/seq66
Architecture: amd64
Depends: libasound2 (>= 1.0.16), libc6 (>= 2.34), libgcc1 (>= 1:3.0), libglib2.0-0 (>= 2.12.0), libjack-jackd2-0 (>= 1.9.5~dfsg-14) | libjack-0.116, libgcc-s1 (>= 3.3.1), libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125, liblo7 (>= 0.26~repack), libqt5core5a (>= 5.15.1), libqt5widgets5 (>= 5.0.2), libstdc++6 (>= 12)
Ahh, just realized there is a debian folder inside the "distros" folder in the source tree. Usually one finds it in the root of the source tree. Don't know how much this is a hard prerequisite, though.
There should be icons in /usr/local/share/pixmap /usr/local/share/seq-0.99/icons and /usr/local/share/seq-0.99/pixmaps. The xfce whisker menu uses one from the first. Maybe enlightenment uses a folder not mentioned?
Ahh, it's there now, sometimes things don't appear in my Menu immediately and a fresh boot this morning brought it up, all good!
Ahh, just realized there is a debian folder inside the "distros" folder in the source tree. Usually one finds it in the root of the source tree. Don't know how much this is a hard prerequisite, though.
Did you use that infrastructure?
I didn't know that was there either. I built it using the autoconf instructions and then made the deb file using dpkg -b after making the file structure.
Ahh, just realized there is a debian folder inside the "distros" folder in the source tree. Usually one finds it in the root of the source tree. Don't know how much this is a hard prerequisite, though.
Did you use that infrastructure?
I didn't know that was there either. I built it using the autoconf instructions and then made the deb file using dpkg -b after making the file structure.
A lot of source code has a Debian folder included, but unless the apps are in actual Repos or PPA's they are often out of date with dependencies or older versions of debhelper and the various package tools that are being used.
Not always... but often enough.. Pretty much anything I package is hand-rolled but to be fair I don't package very many source-built applications, mostly binaries, plugins, scripts, cosmetic stuff etc..
A lot of source code has a Debian folder included, but unless the apps are in actual Repos or PPA's they are often out of date with dependencies or older versions of debhelper and the various package tools that are being used.
Yeah, iirc the debian folks usually recommend to leave the source tree pristine and let the maintainers do their thing.
If i understand it correctly in this case the software was renamed from "seq24" to "seq66" and therefore the debian maintainers can't find the maintained source anymore: https://tracker.debian.org/pkg/seq24
Thanks for taking on a useful project and gaining valuable skillz! The deb installed fine in a recent AVlinux, and the various gui screens opened as expected. I'll have to learn how to use it later, but the more easy to install tools we have, the better!
Cheers