> Date: Sun, 16 Nov 2014 10:50:06 +0000 > From: Ken Moffat <[email protected]> > To: BLFS Support List <[email protected]> > Subject: Re: [blfs-support] Mouse in qemu, > was Re: Configuring terminals in qemu ? > > On Sun, Nov 16, 2014 at 10:18:09AM +0000, akhiezer wrote: > > > Date: Sun, 16 Nov 2014 05:36:26 +0000 > > > From: Ken Moffat <[email protected]> > > > To: BLFS Support List <[email protected]> > > > Subject: [blfs-support] Mouse in qemu, > > > was Re: Configuring terminals in qemu ? > > > > > . > > . > > > Case closed. ;-) But now I've got to try slackbuilds for texlive > > > (can you believe slackware still ships tetex ?) to see if my code to > > > > > > - yep; it builds & installs no-probs; runs well, works well; folks use > > it straightforwardly and hassle-free for writing papers and getting work > > done (TM) - as opposed to, say, faffing around for x months on stabs at > > alternatives; that said, folks use texlive from slackbuilds no probs > > as well (can you believe that some don't? ). I guess that slackware's > > 'K.I.S.S.' principle might, in at least some respects, be a bit too subtle > > for some quarters. > > > > > > > > ;) > > akh > > > > > > p.s. 'can you believe' that some folks still use defunct-isp-branded email > > addresses? Or mutt? &usw. Really, they do .... . Take care ;) . > > > Lol. The point is that tetex has not been maintained since June > 2006.
That's not the point that you made, and that was being gently advised to the contrary on. You're now making (more-)clearly the point re 'unmaint': upstream, yes; and - while "Slackware is not a repository for orphaned software" - at the same time the software is considered to be *_useful_* (i.e. practical, useful) enough for enough people _and_ still builds/installs/runs no-probs s.t. it is not unduly onerous on the slack team, so it is still shipped and *_used_* - who'd'a thunk it, people still using useful tools to do their work (as opposed to pootering around indefinitely). And if you want texlive, it's readily-available from main slackbuilds repos (and there is much overlap of slack team folks and those involved with said repos); and it just works and works well for folks - except seemingly for yourself. > There is a difference between KISS and 'keep it old'. Of course there's a difference; doesn't need saying. But are you implying that Slackware's core motive here is to 'keep it old': that would be nonsense. A central point of 'KISS', of course, is to keep things working well, with minimal hassle - and that includes avoiding putting essentially pointless roadblocks and obstacles in one's own way ... . > As I > said, even the stylesheet for lorem ipsum was missing - and google > can find a 2005 entry for lipsum.html within > tetex-texmf-3.0po.tar.gz so that is not exactly a new addition. > Lorem ipsum: the file's on the system; adjust what you need to do what you need. Slackware pays you the compliment of partway-assuming (some might say, perhaps slightly solipsistically) that if you have special/particular wants from this is or that part of the system, then you'll either know how to do adapt, or be able to get the knowledge readily; and adjustments are usually quite easy, since the platform is very good. Perhaps it should ship without the apparent obstacle that you note again: but many folks are able to use tetex no-probs, for real work (incl collab with folks using texlive and other implems). > My address is still valid, saves having to unsubscribe and then > resubscribe if I change it to whatever my ISP is called this month. > Mutt works well and is still maintained. Yes exactly: they work and are supported; that's exactly the point. If tetex ever became enough of a _genuine_ pita for long enough for the slack team, &/or few enough find it to be genuinely useful, then its probability of being retained would likely decrement a bit. > Of course some people hide > their mailer's identity - that often makes me think they have > something to hide, or else that they are ashamed of what they are > using. What's ... that ... got ... to do with ... the discussion here; seems an at best very loosely-coupled 'point', whether made as a general remark (as the statement is clearly true in that case), or if perhaps as an attempted rejoinder to here (as the statement is clearly false in that case). > > Actually, I'm offended by slackware's choice of console fonts - at :] really, 'offended' ... > first I thought it only offered latin-1 or C fonts, until I realised > that the first few fonts I was offered were .psfu.gz. It is a bit > like looking at how LFS/BLFS used to be : "UTF-8 might not work in > all applications", but because of that it recommends that 'C' is > "safer". FWIW, my own 8x16 font works ok in it. > What argument are you having with yourself, _now_ ... ? Ref above note re adapt/change of the base system. Many sysadmins of servers 'out in the field' will want the shipped default; some others might actually want utf8 for dealings with partic software; x-only folks are basically unaffected; and x/console mixers either select a setup from shipped os, or make simple enhancement/adjustment (ref ibid re doing so); &usw. What exactly is the problem? Is it a roadblock for you? Or what? > ??en akh :| -- -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
