Greetings!
Sorry if this is a stupid question, but every time I think about this I scrape my jaw on the floor and end up blowing fuses in my brain.
Background:
Creating/porting ANY Linux distribution is a Herculean task, and just thinking about the zillions and zillions of packages in the repo's just boggles my mind.
What really sends me into "boggle overdrive" is porting a distribution to a new platform. I've been working on porting, (make that read "making a total mess of porting), the GoPiGo libraries from Raspbery Pi O/S Buster to the Jetson Nano.![:man_facepalming:]()
That, in an of itself, is a Herculean task of non-trivial proportions.
Question: (With respect to the Raspberry Pi and Raspberry Pi O/S.)
How do they do it?!! Simply porting to the ARM platform has to be a huge effort for even ONE package, (and its dependencies).
These guys port the entire kernel, the basic system, and then four-hundred-zillion packages!![:shock:]( "Shocked")
And not just to the ARM platform, but to the quirky and wonky beast that is the Raspberry Pi!
This has gotta represent God Only Knows how many man-years of effort. I remember working on ONE year's version of a famous tax preparation software was almost the entire year's task for dozens and dozens of dedicated development staff, not to mention QA, etc.
The Gimp isn't any less complicated. Scribus is a nice piece of work too. All the good utilities like parted, dd, ddrescue, gparted, e2fsck, and stuff like that - and for stuff like this, there are only two operating modes: Absolutely perfect and "Oh &^%$#@!!!!"
And yet. . . .
And yet. . . .
They make it look soooooo very easy. ([Yawn. . .] Guess it's time to pop out a new respin of Debian [X]. . . Spoiled my nap!)
Will someone help me get my jaw off the floor, (bandages would be nice too), and explain to me how they do it without needing more staff than the entire U.S. Government?
Sorry if this is a stupid question, but every time I think about this I scrape my jaw on the floor and end up blowing fuses in my brain.
Background:
Creating/porting ANY Linux distribution is a Herculean task, and just thinking about the zillions and zillions of packages in the repo's just boggles my mind.
What really sends me into "boggle overdrive" is porting a distribution to a new platform. I've been working on porting, (make that read "making a total mess of porting), the GoPiGo libraries from Raspbery Pi O/S Buster to the Jetson Nano.
That, in an of itself, is a Herculean task of non-trivial proportions.Question: (With respect to the Raspberry Pi and Raspberry Pi O/S.)
How do they do it?!! Simply porting to the ARM platform has to be a huge effort for even ONE package, (and its dependencies).
These guys port the entire kernel, the basic system, and then four-hundred-zillion packages!
And not just to the ARM platform, but to the quirky and wonky beast that is the Raspberry Pi!This has gotta represent God Only Knows how many man-years of effort. I remember working on ONE year's version of a famous tax preparation software was almost the entire year's task for dozens and dozens of dedicated development staff, not to mention QA, etc.
The Gimp isn't any less complicated. Scribus is a nice piece of work too. All the good utilities like parted, dd, ddrescue, gparted, e2fsck, and stuff like that - and for stuff like this, there are only two operating modes: Absolutely perfect and "Oh &^%$#@!!!!"
And yet. . . .
And yet. . . .
They make it look soooooo very easy. ([Yawn. . .] Guess it's time to pop out a new respin of Debian [X]. . . Spoiled my nap!)
Will someone help me get my jaw off the floor, (bandages would be nice too), and explain to me how they do it without needing more staff than the entire U.S. Government?
Statistics: Posted by jharris1993 — Fri Sep 27, 2024 3:59 pm — Replies 2 — Views 84