Hi, First of all, thanks for the great work in ion3, it's really my preferred window manager, and I use it everyday.
I'm writing to the list to ask for advice, specially from Tuomo Valkonen, about how to create ion3 binary packages. As an ion3 fan and archlinux user, I had created a packaging script (this is called PKGBUILD in archlinux - it's a shell script that builds a package) some time ago, so I could easily recommend ion3 to friends that use archlinux too. Until now, I have only distributed this script, but I was planning to distribute pre-built binary packages. So I'm asking here to be sure I'm not infringing Ion trademark license and to be sure I will not attack Ion's reputation or image in any way. The packages will be purely vanilla - it will not include any patches against ion3 source code. It's purely the official released source code. The packaging script is located at: http://aur.archlinux.org/packages/ion-3/ion-3/PKGBUILD It simply builds ion3 with a system.mk file adequate to match the default system directories at archlinux (/usr/bin for binaries, /etc/ion3 for etcdir, etc.). The system.mk file I use is located at: http://aur.archlinux.org/packages/ion-3/ion-3/system.mk When building, the packaging script copies the release date to a script that runs when the user tries to install ion3. This install script is located here: http://aur.archlinux.org/packages/ion-3/ion-3/ion-3.install The install script calls a small Lua snippet to compare the release date against the system clock. If it's more than 28 days older, it displays a message to the user, alerting the package is potentially outdated. I can change this message if you think it could be rewritten in a better way. Should it be enough to produce freely redistributable binary packages? I will always do all I can do to provide the latest version packaged to my friends and to anyone interested in ion3 that uses archlinux, but I would like to be sure there would be no problem before starting to distribute any binary packages. Thanks a lot and best regards, Paulo Matias
