T2_SDE

[oui]

Hi

What is now the status of T2_SDE?

This was long years ago the main build way for new Puppy binaries. Does it continue to be used? If yes, how to do that now?

[wiak]

https://distrowatch.com/?newsid=11592

Don't think it has been used for Puppy for many long years. Last I know was around 14 years ago - Puppy 4 series 2008. Did Puppy Wary still use it?

I have now checked:
https://en.wikipedia.org/wiki/Puppy_Linux

Puppy 5.0.0 - 5.7.0 is based on a project called Woof[21] which is designed to assemble a Puppy Linux distribution from the packages of other Linux distributions. Woof includes some binaries and software derived from Ubuntu, Debian, Slackware, T2 SDE, or Arch repositories. Puppy 5 came with a stripped down version of the Midori browser to be used for reading help files and a choice of web browsers to be installed, including Chromium, Firefox, SeaMonkey Internet Suite, Iron and Opera

But long time ago...
Puppy 5.0.0 15 May 2010
Puppy 5.2.8 4 April 2012
Puppy 5.3.0 - 5.7.0 24 October 2011 - 8 March 2014

Not sure if all these still had T2-SDE variant though. Puppy 5.4 (2012) was 'Precise' version was it not, based on upstream Ubuntu packages?

https://bkhome.org/archive/blog2/tag_puppy-5.html

More on "Precise the next Wary"
July 08, 2013 — BarryK
I raised this possibility recently, and there has been ongoing discussion on the Forum:
http://www.murga-linux.com/puppy/viewtopic.php?t=86384

Instead of slogging on with T2, which I commented earlier is akin to "flogging a dead horse", I am revisiting the idea of repositioning Precise Puppy as the next Wary/Racy.

So I think 2013 was the 'end' of that era: https://oldforum.puppylinux.com/viewtopic.php?t=86384

Some matters have taken an incredibly long time to actually come to pass (dpkg/apt/Synaptic as package manager for the related upstream repos) https://oldforum.puppylinux.com/viewtop ... 19#p710819

For more re: that T2 era, see the old blog archive contents: https://bkhome.org/archive/blog2/all_posts.html
I think this was last mention there (July 2013), and explains problems that were occurring in the 'end' with T2: https://bkhome.org/archive/blog2/201307 ... racy6.html

There is another way that I can approach building a smaller distro... The Debian and Ubuntu packages are so good because there are a huge number of developers, and packages are often heavily patched to fix problems. Precise and Raring pups are good examples. All the old GTK PETs work. I haven't had anything segfault. So, instead of "flogging a dead horse" (T2), another approach is to use Precise pup as the starting point, and recompile packages that have huge dependencies. That way, I can build a smaller pup. It would be a challenge though. My Racy6 .iso is only 131MB with the .sfs file gzipped -- if it had been xz'ed then it would be closer to 100MB. Whereas Raring pup is 177MB xz'ed -- and I shudder to think what that would be if it had been built with gzip'ed .sfs.

I guess the difference in current Puppy dev approach is that not much recompiling of packages that have huge dependencies goes on now? I'm not sure if does or doesn't. I suppose use of more sfs portable packages is the present day alternative to keep underlying Pup smallish whilst making special compiles of bigger packages (presumably using less dependencies than upstream Debian/Ubuntu)? Going back fully to something like T2-SDE sounds like a big task/burden and limiting in terms of available packages? Maybe some middle ground per quoted BarryK paragraph immediately above is still feasible?

[oui]

Hi Wiak

Thank you very much for that precise answer! My question is because T2 did announce in the last days a new version at distrowatch and, if I remember write, BK did continue to use it in some case (Quirky serie?) to generate some or the binaries for those with T2. An if I remember right, there was a depository for the Puppy linux working under T2 processing.

[BarryK]

T2 is a cross-compiler environment. I did use it many many years ago; however, eventually gave up. The last time I tried it, there were too many build failures, it was a real battle.

Instead, I moved to OpenEmbedded, another cross-compile environment. Unlike T2, which is a one-man effort, OE/Yocto has hundreds of developers. I have posted a lot about OE in my blog, and a bit of an intro here:

https://easyos.org/dev/how-to-compile-a ... ource.html

Importing of binary packages compiled in T2 was removed from woof-CE a few years ago, but my woofQ has kept that ability, should it ever be needed, plus added ability to import binary packages compiled by OE.

[oui]

Absolutely fantastic!

Thank you Barry for

https://bkhome.org/news/202112/how-to-c ... edded.html

and all the enormous stuff accessible through that link!