[Privoxy-devel] Contributed binaries

[Lewis G Rosenthal]

Hi, Fabian, and thanks for following up...

On 09/27/22 12:58 pm, Fabian Keil wrote:
> Lewis G Rosenthal <lgrosenthal at 2rosenthals.com> wrote on 2022-09-25 at 23:49:13:
>
>> Seeing that the Team hadn't produced a new OS/2 binary package since the
>> 3.0.21 release, and after building this for myself at the end of
>> January, I thought it might make sense to package it (took long enough;
>> I know).
> Interesting.
>
> Can you describe a bit how you created the package?

Surely.

In general, I used:

gcc.exe (GCC) 9.2.0 20190812 (OS/2 RPM build 9.2.0-5.oc00)

 From there, no changes to any files, just "make".

> Did you need to apply any patches and maybe revert 74f8498812?

I made no changes. Such edits may have been necessary using EMX, but our 
kLIBC environment does a pretty good job these days of providing a complete 
setup. Obviously, there are exceptions (things which stubbornly refuse to 
accept the lack of IPv6 require manual tweaks, for example). However, for 
the most part, many things just build out of the box.

> Did you need third-party software?

All software required to build is freely available via RPM from the Netlabs 
stable repository (http://rpm.netlabs.org/release/00/pentium4/pentium4/).

The does occur to me, however, that I may not have an entirely static build. 
Likely, we'll need libc and friends. Checking...

libcn0.dll
pcrepos0.dll
pthr01.dll
z1.dll
pcre1.dll
gcc1.dll

and their requires, as well. None of this is unexpected today, though I 
should document this before releasing to avoid confusion (yes, along with 
our better compatibility comes dependency h-ll).

> Did you create a OpenPGP signature file?

No, but that's easily remedied.

> Did you run the regression tests with privoxy-regression-test.pl?

I did (Perl 5.16.1):

2022-09-27 13:09:13: Asking Privoxy for the number of action files available ...
2022-09-27 13:09:13: Gathering regression tests from 3 action file(s) 
delivered by Privoxy 3.0.33.
2022-09-27 13:09:13: Executing regression tests ...
2022-09-27 13:09:40: Executed 438 regression tests. Skipped 17. 438 
successes, 0 failures.

As to what was skipped, I'll have to go back and have a closer look.

> Do you intend to stick around to provide support?

I've been involved with OS/2 development since the 1990's, and Arca Noae has 
been in the OS/2 business since 2014. I've never orphaned anything I've 
built for public consumption, so I would say the answer is yes, to the best 
of my ability.

>> Anyway, I'd like to contribute the WarpIN package for distribution from
>> SF (I do have an account there: lewisr). What's the procedure for
>> submission?
> Thanks a lot for the offer.
>
> Technically a team member with SF admin privileges could add your
> account to the SF project and give you upload privileges or you
> could upload the package somewhere and a team member with upload
> privileges could do the upload.
>
> Afterwards I could sync the SF download mirror on the website
> and update the RSS feed.
>
> Before this happens we should probably discuss the details
> and decide if we actually want to provide the package.
>
> For example I used to create and upload binary packages for
> FreeBSD, OpenBSD and NetBSD but as those platforms nowadays
> have a proper package system which is more convenient to
> use the packages were no longer downloaded frequently so I
> stopped providing them again.
>

This is interesting to note. It may be better for us (Arca Noae) to just 
provide an RPM or add the WPI to one of our repos.

> Do modern OS/2 systems have a convenient package system or
> are users still used to download their software from various
> third-party websites like it's done for Windows?
>

It's a mix.

RPMs either come from the Netlabs repositories or the Arca Noae 
repositories. WarpIN installers generally come from third party sites, 
including the Hobbes FTP repository at http://hobbes.nmsu.edu, though new 
functionality (coming soon) to Arca Noae Package Manager (yum GUI) will also 
handle WarpIN installers from known repositories.

> If that's the case it may be preferable to add a hint
> to Privoxy's documentation.

This would surely work, as well, and keep some distance from the upstream 
project, so that you folks don't have to field support inquiries and such 
(even if I ultimately handle any issues).

>> Thanks for this great tool which I've used daily for well over a decade.
> I'm pleased to hear that.
>

You know, it's kind of like the office coffee maker: When it works, nobody 
thinks about it. I actually did this build back at the end of January, and 
have been using it every day since. It's only recently, while testing Squid 
5.7 (I run in a chained configuration) that I even had a second look as to 
where I left off. Good code is like that (it doesn't need a lot of 
attention, and generally behaves itself). ;-)

Cheers

-- 
Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE, CWTS, EA
Rosenthal & Rosenthal, LLC                www.2rosenthals.com
visit my IT blog                www.2rosenthals.net/wordpress
-------------------------------------------------------------