rc: unix bits removed

rc: unix bits removed

[stanley lieber]

I haven't had a chance to look at this yet, but does/did the p9p/9base rc rely upon the UNIX bits that were just removed from 9front rc?

sl

Re: [9front] rc: unix bits removed

[cinap_lenrek]

do you mean that some 9base package refers to files from 9front
mercurial tip?

Ori_B tried to build rc for unix, failed and i conclused it was broken
and removed the files, assuming anyone who wants rc for windows or
unix knows where (not) to find it :)

just like with drawterm, i'm not going to maintain unix and window
shit in the 9front tree. it just leads to unmaintained broken shit
that makes changes harder as i have to do changes in files that i
can not build to test...

--
cinap

Re: [9front] rc: unix bits removed

[stanley lieber]

>do you mean that some 9base package refers to files from 9front
>mercurial tip?

No, I was asking (without having checked) if the p9p/9base rc uses those files from whatever version of rc they are derived. The reason I asked is because whenever I have time I will be trying to sync frontbase (our fork of 9base) with 9front. I was wondering if the job just got harder.

It's likely I'm not qualified for the job in the first place.


>Ori_B tried to build rc for unix, failed and i conclused it was broken
>and removed the files, assuming anyone who wants rc for windows or
>unix knows where (not) to find it :)

Which UNIX? I get the criteria you outline below, but this seems like a convenient excuse. :)


>just like with drawterm, i'm not going to maintain unix and window
>shit in the 9front tree. it just leads to unmaintained broken shit
>that makes changes harder as i have to do changes in files that i
>can not build to test...

How do you build UNIX and Windows drawterm to test?

sl

Re: [9front] rc: unix bits removed

[cinap_lenrek]

>>do you mean that some 9base package refers to files from 9front
>>mercurial tip?

> No, I was asking (without having checked) if the p9p/9base rc uses those files
> from whatever version of rc they are derived. The reason I asked is because whenever
> I have time I will be trying to sync frontbase (our fork of 9base) with 9front.

excellent, do it. if nobody maintains the unix parts, then theres no reason to keep
it in the 9front repository. once theres a known working version again, i'm happy
to sync it back. but i dont see a reason to maintain known broken shit when theres
a p9p version out there that already works.

> I was wondering if the job just got harder.

no, i dont think so.

> It's likely I'm not qualified for the job in the first place.

just DO IT.

>>Ori_B tried to build rc for unix, failed and i conclused it was broken
>>and removed the files, assuming anyone who wants rc for windows or
>>unix knows where (not) to find it :)

> Which UNIX? I get the criteria you outline below, but this seems like a convenient excuse. :)

linux with p9p. symbol clash with searchpath().

>>just like with drawterm, i'm not going to maintain unix and window
>>shit in the 9front tree. it just leads to unmaintained broken shit
>>that makes changes harder as i have to do changes in files that i
>>can not build to test...

> How do you build UNIX and Windows drawterm to test?

from the drawterm repo.

> sl

--
cinap

Re: [9front] rc: unix bits removed

[stanley lieber]

>> It's likely I'm not qualified for the job in the first place.
>
> just DO IT.

Two problems:

1. I don't know what I'm doing

2. These days, I have less than zero time.

They've made it so we can't have personal computing devices or Internet at work AT ALL, and when I'm at home I'm completely occupied with family stuff.

Eventually, I will try to do it.

sl

Re: [9front] rc: unix bits removed

[hiro]

i think it's fair.
if your customers can't have internet, why should you.
eating your own shit, etc.

Re: [9front] rc: unix bits removed

[cinap_lenrek]

rc hasnt changed in a long time, and the GLOB escaping bugs i fixed where
in there for a very long time without anyone complaining.

so theres no rush...

--
cinap