Yes, i tried but i prefer use tde on a debian base. Try by your own :) Le 29 oct. 2014 20:23, "Dr. Nikolaus Klepp" <office(a)klepp.biz> a écrit :

FreeBSD sounds like a possibility (and no systemd). Thinking of installing to see about running TDE in it. But its boot image requires a MBR primary or GUID partition. So I would have to back up my disk in order to convert to GUID partitioning...one thing leads to another...will consider it...Robert

On 1 November 2014 14:00, Dr. Nikolaus Klepp <office(a)klepp.biz> wrote: Another way to go is Gentoo, though it takes some work and close attention to the installation manual. I used it for a while ten years ago and am looking at it again. I wonder what experience others have had with it. Robert

On Sat, 1 Nov 2014 18:03:54 -0600 Robert Peters <robertpeters9(a)gmail.com> wrote: I've been using Gentoo for . . . nine years now? Something like that. It's a functional distribution if you're comfortable with the command line and willing to ignore the periodic flare-ups of developer drama backstage. Openrc is a solid enough init system (not as fast as I understand systemd can be set up to be, but as far as I'm concerned that's a feature), and Gentoo isn't likely to give it up any time soon. I've also opted for eudev rather than standard udev on two boxes, and haven't had any problems with that either. Unfortunately, the most complete set of Trinity packages for Gentoo ( https://github.com/Fat-Zer/trinity ) is somewhat out of date. Tweaking the ebuild version numbers may be enough to let most packages build, though. In general, the continued existence of the (increasingly broken) kde-sunset overlay complicates Trinity's status with respect to Gentoo. E. Liddell

Date: Sun, 2 Nov 2014 08:15:49 -0500 From: ejlddll(a)googlemail.com To: trinity-users(a)lists.pearsoncomputing.net Subject: Re: [trinity-users] q4os On Sat, 1 Nov 2014 21:30:24 -0500 "Timothy Pearson" &lt;kb9vqf(a)pearsoncomputing.net&gt; wrote: Gentoo's general philosophy is that choice is a Good Thing, so the overlay would probably not be unwelcome. The trick is getting it into the official list. This is far from impossible, but the documentation for doing it seems to have moved without leaving a forwarding address, so it might require contacting #gentoo-portage or the dev mailing list directly. Whatever overlay we produced would end up being offered in addition to kde-sunset rather than replacing it (that's just how the system works), but there's nothing intrinsically wrong with that. The only thing you need to host an overlay is a version control system, and we've got that covered. Now, let me back up and explain a bit more about Gentoo for anyone who may be reading this over our shoulders: Gentoo is a rolling-release, source-based distribution that allows the user to select build options. With only a handful of exceptions, all packages are compiled on the user's machine. The Gentoo package format--the ebuild--is unique to Gentoo and a few of its descendants, and consists of a bash shell script containing build instructions to be interpreted with the assistance of the package manager. Really, it's a specialized programming language built on top of a bash + python stack. Gentoo also has a bunch of other quirks involving directory structure and such--probably not that many more than some other distributions, but they all have to be accounted for. Ebuilds can involve directory moves, patches, sed, and more. Outside package repositories in Gentoo are known as overlays, and are managed through a tool called layman. There's a semi-official list of overlays (the layman registry) that includes everything from developers' private playgrounds to entire descendant distributions. Getting an overlay onto that list is a key factor in making users aware that it exists. </digression> Thankfully, we already have ebuilds for the bulk of Trinity, even if they are slightly dated, and getting most of them working for V14 really is likely to be just a matter of renaming the ebuild files, which include the version number as a matter of course. (This assumes that the source tarball naming convention stays consistent--but even if it doesn't, that's a fairly straightforward one-line tweak.) The exceptions will be any packages that moved from autotools to cmake after Fat-Zer's last ebuild for said package. Those will have to be redone, and I'm not sure we have anyone adequate to the task. I don't think we have any other Gentoo users active on our dev-list right now, and my ebuild skills are so-so at best--I specialize in the wrong programming languages and have a limited understanding of the C/C++ build toolchain. Which is why my packaging attempt back in the day fell flat. Fat-Zer seems to have done at least some of the work that was beyond my capacity, but I'm not sure how complete it is. When KDE3 was still in Gentoo's main package hierarchy, it was maintained by the KDE herd, which I believe typically has 10-12 members. The reason kde-sunset's been bit-rotting to the point that some packages are no longer compilable is the lack of a core group of maintainers--given the sheer number of packages involved, one or two people just aren't enough. And I don't think most of the kde-sunset users remaining are at all knowledgeable about ebuild development, or the overlay wouldn't have deteriorated so much. (In other words, the problem with creating an overlay is going to be maintaining it properly.) On the bright side, supporting Gentoo adds no extra load to the build farm, and if we can get things together well enough to provide live ebuilds (pulling directly from the git source) in addition to stable ones, we might get a few more testers. We might also get some interest from some of the rarer architectures KDE3 used to be able to run on (alpha, mips, ppc, Itanium . . .), since they are officially supported by Gentoo, meaning that there are Gentoo developers and users who have the needed test hardware. If we are going to do this, I suggest concentrating on the actual TDE packages and a handful of the most popular third-party applications (amaroK, K3B, kaffeine to start with) and adding other third-party software by request. That's still ~100 packages, I think, since the core packages are split into individual applications with their own ebuilds. E. Liddell

From: robertpeters9(a)gmail.com Date: Sun, 2 Nov 2014 09:32:11 -0600 To: trinity-users(a)lists.pearsoncomputing.net Subject: Re: [trinity-users] q4os On 2 November 2014 07:49, Alexandre &lt;ac586133(a)hotmail.com&gt; wrote: <snip> Re Gentoo: I read E. Liddell's post with great interest and am interested to help but maybe don't have the knowledge, skills and test hardware to do so. Re PCLinuxOS: recently I burned the live DVD image to bootable USB stick and tried to install; it hung after a single line of text. I might have done it wrong and am willing to try again. Robert

I have found unetbootin to be problematic with various isos, because of this I use dd and have never had a problem since.

Bugger! This is not a live image! You cannot "try before you install"

Hi Robert, Thank you for taking the time to try my remaster. Unfortunately, I am not 100% sure that PCLinuxOS is compatible with tools like UnetBootin for usb keys. Can you try it directly on a computer with an optical drive? Also, from my experience as an Asus EEE user, unetbootin does not work all the time on first try. I also got better results by not touching to the computer while unetbootin copy the data.