@Rich: Opinion received and well taken.
Argument: The next time there's an ARM kernel compilation, a new(ish) version is presented in the repo (say 14.x) and people start learning of its existence.. while Béla is getting nailed to the cross with the barrage of posts saying "where's this extension?" and "isn't it compiled yet?" this is where we decided to leave the poor guy alone and experiment with tce-load/ab and more times than not, it's successful. Yes, there are going to be those extensions which get broken when ncurses.tcz gets revamped and renamed to ncursesw.tcz and a few of the functions which used to be part of the package are now found in separate dependencies scattered around the universe (etc. -- that's just a rant from a recent TCL Apache/LAMP build that went South.
)
Example: We use dropbear for in-house SSH; back in v6 through v8 it went MIA within the repo; and I think it reappeared in 9.x. Instead of hunting, or God forbid hounding an already overworked crew "Hey, where's my bear?" we re-used 5.x's copy throughout the different versions without a hitch. Actually, 9.x might have even been our submission; I can't recall.
As for x86/x64 "...you can't mix..." maybe you can clarify something for me?
I recall posts from WAY back when that had discussed opting for x86_64 to be created in TC, different approaches, etc. and maybe there's been assumptions fed from dusty memories, but if x86 is strictly 32 bit kernel/user and x64 is strictly 64 bit kernel/user, what are the filename64 items doing in 12.x/x86/release/distribution_files? (I thought these were supposed to be something like 64b kernel / 32b userspace where x86 extensions would operate, but I also recall someone noting it wasn't like M$'s WoW/emulation/etc.?)
Regardless, thanks for your input and efforts!
Mr. T. J. Glawitsch -- President
American Networks, Assoc.
CentralWare Development Centers
Welcome
FAQ
Downloads
Wiki
