From: "Charles P. Schaum" <verbo.solo@sbcglobal.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: distro info
Date: Sat, 14 Jun 2008 18:32:21 -0500 [thread overview]
Message-ID: <1213486341.17464.5.camel@elbereth> (raw)
In-Reply-To: <71B80F45-F295-4029-83D5-75E5260EA5CB@fiee.net>
What could perhaps occur is this:
Get PC-BSD's PBI technology working with something like DarwinPorts or
whatever BSD ports tree exists for the Mac. IIRC, they now have a
relatively automated way of getting from ports to PBI's.
But you would need cooperation, legal protection or licensing for the
PBI tech, some currency at hand to pay a developer, and a committed,
tech-savvy crew. And this might not fly because PBI is the special deal
for PC-BSD. Would they "share" for Mac?
But a ConTeXt PBI would make me look at the BSD's a little more. I don't
really want TeTeX and staying current with CTAN pretty much precludes
depending on a "distro" anyway.
Charles
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-14 23:32 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 14:36 Andrea Valle
2008-06-10 14:43 ` Andrea Valle
2008-06-10 15:29 ` Wolfgang Schuster
2008-06-10 15:30 ` Otared Kavian
2008-06-10 15:34 ` Hans Hagen
2008-06-10 17:21 ` David
2008-06-10 17:37 ` Hans Hagen
2008-06-10 20:31 ` Andrea Valle
2008-06-12 1:22 ` David
2008-06-12 7:51 ` Olivier Guéry
2008-06-12 8:58 ` Mojca Miklavec
2008-06-10 15:58 ` Mojca Miklavec
2008-06-10 20:27 ` Andrea Valle
2008-06-10 21:08 ` Mojca Miklavec
2008-06-11 12:09 ` Oliver Buerschaper
2008-06-11 14:55 ` Andrea Valle
2008-06-11 16:05 ` Mojca Miklavec
2008-06-11 16:55 ` Andrea Valle
2008-06-11 20:43 ` Jesse Alama
2008-06-12 9:00 ` Andrea Valle
2008-06-13 16:40 ` Henning Hraban Ramm
2008-06-13 17:08 ` Andrea Valle
2008-06-13 18:01 ` Mojca Miklavec
2008-06-13 18:20 ` Henning Hraban Ramm
2008-06-13 18:26 ` Matthias Weber
2008-06-13 19:23 ` Henning Hraban Ramm
2008-06-13 17:57 ` Thomas A. Schmitz
2008-06-14 11:07 ` Oliver Buerschaper
2008-06-14 11:35 ` Thomas A. Schmitz
2008-06-14 13:57 ` Andrea Valle
2008-06-14 17:36 ` Thomas A. Schmitz
2008-06-14 21:38 ` Henning Hraban Ramm
2008-06-14 23:32 ` Charles P. Schaum [this message]
2008-06-14 14:19 ` Oliver Buerschaper
2008-06-14 16:35 ` Jesse Alama
2008-06-14 18:59 ` Mojca Miklavec
2008-06-14 23:05 ` Diego Depaoli
2008-06-15 0:41 ` Charles P. Schaum
2008-06-15 1:36 ` Matthias Weber
2008-06-15 9:40 ` Andrea Valle
2008-06-30 5:27 ` Jesse Alama
2008-06-30 7:03 ` Alan Stone
2008-06-30 8:20 ` Mojca Miklavec
2008-06-30 16:21 ` George N. White III
2008-06-14 11:48 ` Andrea Valle
2008-06-14 13:55 ` John Culleton
2008-06-17 16:02 ` searchable pdf in mkii, usepdffontresource stub Oleg Kolosov
2008-06-17 16:34 ` Hans Hagen
2008-06-17 18:55 ` Oleg Kolosov
2008-06-17 19:13 ` Hans Hagen
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=1213486341.17464.5.camel@elbereth \
--to=verbo.solo@sbcglobal.net \
--cc=ntg-context@ntg.nl \
/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).