Re: [Freedos-devel] DOjS update and size suggestions

2024-11-29 Thread Jerome Shidel via Freedos-devel
Hi, > On Nov 30, 2024, at 1:31 AM, Mercury Thirteen via Freedos-devel > wrote: > > The UPX issue would be irrelevant if we didn't ship binaries at all. Hear me > out. :) > > Repeatedly, I have seen stressed here the importance of making sure all > packages we ship are 100% open source. And r

Re: [Freedos-devel] DOjS update and size suggestions

2024-11-29 Thread Mercury Thirteen via Freedos-devel
The UPX issue would be irrelevant if we didn't ship binaries at all. Hear me out. :) Repeatedly, I have seen stressed here the importance of making sure all packages we ship are 100% open source. And rightfully so - I don't disagree with that. However, shipping binaries could be seen as a form

Re: [Freedos-devel] FreeDOS 1.4 (recompiled upx)

2024-11-29 Thread Paul Dufresne via Freedos-devel
Le ven., 29 nov. 2024 21:55:18 -0500 Michael Brutman via Freedos-devel a écrit > I don't understand what the problem with UPX compressed executables is. I don't think it is really a legal issue. The problem as I see it, is that we have a program that modify executables, in an hidden

Re: [Freedos-devel] Make make great again!

2024-11-29 Thread Jerome Shidel via Freedos-devel
Hi Jim, > On Nov 29, 2024, at 7:24 PM, Jim Hall via Freedos-devel > wrote: > > [..] > D:\SRC\MAKE-0.0>WCC -q getopt~1.c > > [no messages] > > D:\SRC\MAKE-0.0>WCC -q make.c > [.. couldn't copy/paste all of the output from QEMU..] > make.c(606): Error! E1063: Missing operand > make.c(606): Warn

Re: [Freedos-devel] FreeDOS 1.4 (recompiled upx)

2024-11-29 Thread Michael Brutman via Freedos-devel
I don't understand what the problem with UPX compressed executables is. The authors grant you (anybody) a license to compress a program using UPX and to make use of their decompression code (the stub) as long as you use their unmodified code. Non open code may use the stub for its intended purpos

Re: [Freedos-devel] Make make great again!

2024-11-29 Thread Jim Hall via Freedos-devel
Rugxulo wrote: >> Since there is no binary included, but it relies on the GNU AutoTools >> to build (presuming a native POSIX toolset and Sh that is not fully >> working together on native DOS with DJGPP), can you please compile >> this for us? (I think even GNU Make used to come with a .BAT to >>

Re: [Freedos-devel] How would one go about getting a package added?

2024-11-29 Thread Jim Hall via Freedos-devel
I didn't see a reply to Kirn's email so I figured I'd jump in: On Mon, Nov 11, 2024 at 5:23 PM Kirn Gill via Freedos-devel wrote: > > [..] > I'd like to get a program I'm working on into the FreeDOS package > repository. It's a utility program that reads out headers of executable > files, and is

Re: [Freedos-devel] DOjS update and size suggestions

2024-11-29 Thread Jim Hall via Freedos-devel
On Mon, Nov 25, 2024 at 7:04 PM Eric Auer via Freedos-devel wrote: > > > Hi! There is a new DOjS release, as mentioned on > > https://sourceforge.net/p/freedos/news/ > > unfortunately, the freedos zip is 61 MB in size :-o > > https://ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/js/dojs/1.13.

Re: [Freedos-devel] FreeDOS 1.4

2024-11-29 Thread Jim Hall via Freedos-devel
It's been two weeks and I've been away from email lately, so I am checking if I missed an announcement. Did these programs get released/announced anywhere? I did a quick check of my Inbox and I don't see announcements to freedos-devel for the kernel, country.sys, format, freecom, or tree. But mayb

Re: [Freedos-devel] FreeDOS 1.4 (recompiled upx)

2024-11-29 Thread Jim Hall via Freedos-devel
On Tue, Nov 26, 2024 at 2:36 PM Paul Dufresne via Freedos-devel wrote: > > I said: > > Note the license seems to allows rebuilding and distributing only a > > not-modified version. > I did read too fast the license... You can read it at: > https://github.com/upx/upx/blob/devel/LICENSE > It's a b