From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] drawterm source?
Date: Thu, 18 Jun 2015 08:16:01 -0500 [thread overview]
Message-ID: <46B9E4BB-F0D9-4837-8D78-427A8A4A2213@corpus-callosum.com> (raw)
In-Reply-To: <CANUoZoFwKEArJWDycoWLwfW2-osspX_7bFX5e6DaGLR0gBwK6g@mail.gmail.com>
> On Jun 18, 2015, at 7:47 AM, David du Colombier <0intro@gmail.com> wrote:
>
>> so why do we have so many un-coordinated versions of drawterm?
>
> Because the original repository is hosted on Bitbucket (and Google Code),
> and Russ won't accept to review changes on Rietveld anymore.
For the same reason there are so many forks of everything else, everyone
is [wants to be] a diva.
But in reality, the multiple targets (X11 on various platforms/versions,
OSX pre- and post-Carbon, iOS, and Windows) all have differences that don’t
always integrate into the same build system. I tried to keep the drawterm-
cocoa port viable across all targets, but after a migration of more current
libraries over from Plan 9 I never completed the X11 or Windows integration
to get those build. Never completed for two reasons, I don’t have a Windows
environment to build/test, nor are any of my X11 targets consistent: one
build on an old Ubuntu works, a newer Ubuntu doesn’t, nor the differing
versions of X11 on my various FreeBSD releases I can test. And don’t even
get me started on the differing distros for Linux or testing for CDE/GNOME/
KDE/Unity/Xfce…
I’ve never pushed the X11 changes to support rio resizing as I just don’t
have a host (or time) to test.
> So, I've simply moved it to GitHub.
Maybe it is nice that Git is winning the DVCS wars. That said, there needs
to be an effort to port that beast to Plan 9 for those of us who still use
that platform for research and development.
-jas
next prev parent reply other threads:[~2015-06-18 13:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 23:32 Steve Simon
2015-06-14 23:55 ` Skip Tavakkolian
2015-06-17 15:15 ` Steve Simon
2015-06-18 10:18 ` Michaelian Ennis
2015-06-18 10:25 ` Michaelian Ennis
2015-06-18 10:33 ` David du Colombier
2015-06-18 10:41 ` David du Colombier
2015-06-18 12:37 ` erik quanstrom
2015-06-18 12:42 ` Kurt H Maier
2015-06-18 12:47 ` David du Colombier
2015-06-18 13:05 ` lucio
2015-06-18 13:16 ` Jeff Sickel [this message]
2015-06-18 13:56 ` michaelian ennis
2015-06-18 13:01 ` lucio
2015-06-18 14:20 ` Kurt H Maier
2015-06-18 14:23 ` Steve Simon
2015-06-18 15:29 ` Skip Tavakkolian
2015-06-18 14:03 hiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46B9E4BB-F0D9-4837-8D78-427A8A4A2213@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).