Re: [9fans] Update APE

2017-02-20 Thread Kurt H Maier 
On Tue, Feb 21, 2017 at 02:59:27AM +, Skip Tavakkolian wrote:
>
> It begs the question of how do we organize a community maintained 
> repository?

There isn't "a" community, so it's pretty pointless.  The list you
posted is the complete list of stuff that matters with the possible
exception of Forsyth's 9k repository [1], which doesn't appear to have
got much updating recently.  The point is, there's not that much to keep
track of, and anyone who cares will not have a terrible time keeping up.

The only time this has failed me was when a 9legacy patch written
specifically for Go took us by surprise (we got users mentioning a
release candidate wouldn't build).  I whined on Go's issue tracker and
they promised to mention such breaking changes in the release notes.[2]

In short, the people who give a shit about revision control are already
using it, the SP9SSS isn't going to start using it in public, and trying
to get everyone under one tent isn't going to work because git hipsters
literally suffer from organ failure when you ask them to try mercurial,
even though there isn't a (public) git port for Plan 9.

What it boils down to is two classes of makework:  watch the commit logs
for 9k[1] and 9front[3], and write a script that automates pulling
9legacy's patch list or 9atom's image and diffing them for you.  Both 
9k and 9front have facilities for having commit logs mailed to you, if 
you'd prefer.  They both also support rss/atom feeds.  

khm





[1] https://bitbucket.org/forsyth/plan9-9k

[2] Instead we got instructions to read the Go wiki, which documents
required Plan 9 changes and when some were put in, but not which
particular Bavarian fire drill affects which particular release of Go.  
But this is a Go problem, not a failure of the Plan 9 world.  And the
wiki is better than nothing.

[3] http://code.9front.org/hg/plan9front/

Re: [9fans] Update APE

2017-02-20 Thread Skip Tavakkolian 
9p.io mirrors sources.

On Mon, Feb 20, 2017, 7:54 PM Lyndon Nerenberg  wrote:

>
> > On Feb 20, 2017, at 6:59 PM, Skip Tavakkolian <
> skip.tavakkol...@gmail.com> wrote:
> >
> > 9pi (bcm) kernel: maintained by Richard Miller; sources are in contrib
> area on Labs' sources
>
> We really need to make sure the Labs' public fileserver is getting
> mirrored someplace.  I doubt it will be very long before it vanishes
> altogether.  (I'm surprised it's still around, in fact.)
>
>
>

Re: [9fans] Update APE

2017-02-20 Thread Lyndon Nerenberg 

> On Feb 20, 2017, at 6:59 PM, Skip Tavakkolian  
> wrote:
> 
> 9pi (bcm) kernel: maintained by Richard Miller; sources are in contrib area 
> on Labs' sources

We really need to make sure the Labs' public fileserver is getting mirrored 
someplace.  I doubt it will be very long before it vanishes altogether.  (I'm 
surprised it's still around, in fact.)

Re: [9fans] Update APE

2017-02-20 Thread Skip Tavakkolian 
David du Colombier has kept up a comprehensive list of patches at 9legacy (
https://www.9legacy.org/patch.html); it's the best place to start.

Although patches can still be submitted to Labs' sources, the last time any
kernels in that repository were updated was in 2014. Fortunately there are
other maintained distributions[*]
I'm not sure how patches made in one distribution make their way into other
distributions.

I don't know how long this form of patches against Labs' frozen version
would be possible.  As patches pile on, a set of deltas need to be kept
going back to the Labs' sources.  It begs the question of how do we
organize a community maintained repository?

[*] list of Plan 9 distro's I'm aware of:
9legacy distro: maintained by David du Colombier
9front distro: kept up by ɔᴉuɐd lǝuɹǝʞ and 9 people's front people
9atom distro: kept up by Erik Quanstrom
9pi (bcm) kernel: maintained by Richard Miller; sources are in contrib area
on Labs' sources



On Mon, Feb 20, 2017 at 4:47 PM Steve Simon  wrote:

> sadly there doesn't seem to be a way to add users to the labs sources
> server,
> unless somone knows different.
>
> I think the best thing would be to post diffs to this mailing list.
>
> I have some small changes to APE I have been meaning to post, nothing
> substantial
> mut enough to make porting some tools easier.
>
> -Steve
>
>

Re: [9fans] Update APE

2017-02-20 Thread Steve Simon 
sadly there doesn't seem to be a way to add users to the labs sources server,
unless somone knows different.

I think the best thing would be to post diffs to this mailing list.

I have some small changes to APE I have been meaning to post, nothing 
substantial
mut enough to make porting some tools easier.

-Steve

Re: [9fans] Replace Lucida Fonts

2017-02-20 Thread hiro 
vga

Re: [9fans] Update APE

2017-02-20 Thread Jens Staal 
If someone could backport apex from Harvey, that would be cool.

Den 20 feb. 2017 19:50 skrev "Charlie Lin" :

> Since the POSIX standard is updated to POSIX.1-2008 with the 2016 TC, the
> commands should be updated as well.
>
> Also, how to submit either a patch or a contribution?
>

[9fans] Update APE

2017-02-20 Thread Charlie Lin 
Since the POSIX standard is updated to POSIX.1-2008 with the 2016 TC, the
commands should be updated as well.

Also, how to submit either a patch or a contribution?

[9fans] Replace Lucida Fonts

2017-02-20 Thread Charlie Lin 
Since the Lucida fonts distributed with the OS are not redistributable when
alone (and thus not open-source), what alternatives are available?

I suggest the Liberation font family.