https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/
Seems interesting. Maybe we can generate a build summary of failed packages for termux-packages. Will surely look into this after my exams
Sooo, funding.
We discussed opencollective and liberapay a bit before. I'm thinking that opencollective would be a good option, we can then make a budget for monthly expanses (which we don't have a lot of, maybe part of my vps cost or part of the email host cost), and also one-time expanses, which could for example be funding for purchase of a device for testing for agnostic-apollo , or perhaps a reward for potential vulnerability fixes.
They have a open-source specific plan: https://opencollective.com/opensource, and all the fine print can be read here, and looks reasonable to my non-lawyer mind.
Any questions/comments/objections, from anyone, on the suggestions to create an open collective?
OSC will exercise full control over the Project’s financial administration, management, and disbursement of the Fund and any Other Assets. OSC shall have the right to deduct Project Dues and Expenses, as defined by the Protocols, directly from the Fund without further approval by the Collective.
So they own us from henceforth! ;)
Dues consist of:
i. 10% of all of the funds deposited into the Fund, regardless of source, as an administrative fee; and
ii. All interest earned on the Fund which will be retained in OSC’s general fund.
So they will be investing our big monies too and keeping it all!
By yeah, looks reasonable from my non-lawyer mind too.
Dobby233Liu > Note that DOSBox-X suports both SDL 1.x and 2.x, and it is written to compile against the in-tree copy of the SDL 1.x (Simple Directmedia Libary), or against the SDL 2.x library provided by your Linux distribution.
For Visual Studio and MinGW compilation, the in-tree copy of SDL is always used. Note that the in-tree SDL 1.x library has been heavily modified from the original SDL 1.x source code and is thus somewhat incompatible with the stock library.
The modifications provide additional functions needed to improve DOSBox-X and fix many issues with keyboard input, window mangement, and display management that previously required terrible kludges within the DOSBox and DOSBox-X source code.
i think they prefer the sdl1 version (its currently the default also) but i cant decide
Dobby233Liu they actually run configure within their special build scriptwait so i do
./build $TERMUX_PKG_EXTRA_CONFIGURE_ARGS ?
marcusz No but there's some exampleshttps://github.com/termux/termux-packages/blob/5405b3d873ed3035847da7a15e1e74c40e58c3c3/x11-packages/xrdp/build.sh#L11
Dobby233Liu i am still confused on what to do
my build script has this
termux_step_configure() {
# configure is run in the build step
}
termux_step_make() {
./build \
--enable-sdl \
--disable-fpu-x86 \
--disable-fpu-x64 \
--disable-dynamic-x86 \
--disable-opengl
}and their build script is like this https://github.com/joncampbell123/dosbox-x/blob/dosbox-x-v0.83.25/build , which generates the configure script, compiles the in-tree libraries, and configure (passing through the parameters passed to the script) then build, my question is is putting the configure args in termux_step_make like this fine
./build, but write a build script for the termux build system. For example, putting what you put after ./build (and what after ./configure in ./build that are appropriate in termux, like --enable-core-inline but not --prefix=/usr) in TERMUX_PKG_EXTRA_CONFIGURE_ARGS
Dobby233Liu i think i just ran ./build back when i was manually building the programhttps://github.com/joncampbell123/dosbox-x/issues/2658#issuecomment-877770868 tells nothing
Dobby233Liu oh that might patch some stuff right
Dobby233Liu alright i got this error while building the package on device
ERROR: lib/libX11.so contains undefined symbol libandroid_shmctlany idea what is happening
Dobby233Liu termux-info and build log just-in-case
Termux Variables:
TERMUX_APK_RELEASE=GITHUB
TERMUX_APP_PID=18783
TERMUX_IS_DEBUGGABLE_BUILD=1
TERMUX_MAIN_PACKAGE_FORMAT=debian
TERMUX_PKG_MAINTAINER=Liu Wenyuan <15816141883@163.com>
TERMUX_VERSION=0.118.0
Packages CPU architecture:
x86_64
Subscribed repositories:
# sources.list
deb https://packages-cf.termux.org/apt/termux-main/ stable main
# x11-repo (sources.list.d/x11.list)
deb https://packages.termux.org/apt/termux-x11 x11 main
Updatable packages:
All packages up to date
Android version:
9
Kernel build information:
Linux localhost 4.4.124+ #1 SMP PREEMPT Mon Jun 18 17:10:07 UTC 2018 x86_64 Android
Device manufacturer:
unknown
Device model:
Android SDK built for x86_64https://cdn.discordapp.com/attachments/847704138711171084/974999757284057118/build.log
Dobby233Liu actually wait
Dobby233Liu the log seems to miss some stuff
! Ei i have noticed that the swrast driver was enabled in mesa, maybe we could enable glx in xserver rather than using the xlib method now?
Can we mandate either of the following format for TERMUX_PKG_MAINTAINER field? :
- only github username
- or
@github-username <email>
It would be useful to automate assigning respective issues to there maintainers (For example in failing auto-updates).
Aditya Alok: the format "Henrik Grimler grimler@termux.org" is pretty standard and looks good, using github handle instead of name definitely makes sense in this case, so sounds good to me.
Unfortunately we won't be able to assign non-organisation maintainers I suppose, unless perhaps if we invite people as external collaborators
email (name) format since less chances of breakage. Can also add github username after name.