OS/2, eCS & ArcaOS - Technical > Internet

Experimental build of SeaMonkey

<< < (2/16) > >>

Martin Iturbide:
Hi Rich.


--- Quote from: Rich Walsh on November 26, 2017, 05:41:27 pm ---...Why would anyone advocate confining them to the bloated and largely pointless @unixroot tree unless absolutely necessary? Group-think? A fondness for arrogant and authoritarian mindset that BWW unfailingly displays?

--- End quote ---

I had also presented my dislike of "Filesystem Hierarchy Standard" many times in the past. Even some groups of the Unix world dislike it. But on our case (The OS/2 platform) I think that the issue was that we became dependent of many Linux ports libraries and even that everything can be reorganized on a better structure it was very difficult to maintain a different layout only for OS/2 because of the lack of resources we have on this platform.

We had a lot of DLL versioning issues and RPM was a good solution to keep all that updated, but it came with a cost. It was to much of chore to have RPM customized to have a different FHS on OS/2. So for me it was to "suck it up" with FHS or try to find resources that wanted to maintain a customized RPM version only for OS/2 and that verifies that every ported/updated DLL works on that new structure.

Regards 

André Heldoorn:

--- Quote from: Martin Iturbide on November 27, 2017, 05:58:37 pm ---
--- Quote from: Rich Walsh on November 26, 2017, 05:41:27 pm ---...Why would anyone advocate confining them to the bloated and largely pointless @unixroot tree unless absolutely necessary? Group-think? A fondness for arrogant and authoritarian mindset that BWW unfailingly displays?

--- End quote ---

I had also presented my dislike of "Filesystem Hierarchy Standard" many times in the past. Even some groups of the Unix world dislike it.

RPM was a good solution to keep all that updated, but it came with a cost.
--- End quote ---

</silence>
If the number of lines of output exceeds 100, then using STDOUT instead of STDERR hardly requires resources. Of course there are more optional ways to OS/2'ify software. Icon, installer, documented data file search strategies not assuming an @Unixroot, deleting useless files, avoided useless requirements of requirements (like a HUNSPEL0.DLL without any installed dictionary), and so on.

I'll try to care less, but does a RPM release actually manage e.g .the lxLite package, including all documentation files, of eCS 2.x?
<silence>

roberto:

--- Quote from: Dave Yeo on November 27, 2017, 02:06:43 am ---Hopefully the link is fixed.

--- End quote ---
Well, the link does not work for me. ??
saludos

Dave Yeo:
What about if you start at https://bitbucket.org/dryeo/dry-comm-esr31/downloads/

R.M. Klippstein:
Hi Dave , latest link doesn't work here also. The Inet has been really slow and unrelieable her lately -- don't know what gives!

klipp

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version