[9fans] Applying patches to local machine

[9fans] Applying patches to local machine

[Christian Kellermann]

[-- Attachment #1: Type: text/plain, Size: 211 bytes --]

Hi,

is there an easy way to apply patches from sources to my local machine?

Regards,

Christian

-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] Applying patches to local machine

[Charles Forsyth]

[-- Attachment #1: Type: text/plain, Size: 73 bytes --]

see http://plan9.bell-labs.com/wiki/plan9/Staying_up_to_date/index.html

[-- Attachment #2: Type: message/rfc822, Size: 3709 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 211 bytes --]

Hi,

is there an easy way to apply patches from sources to my local machine?

Regards,

Christian

-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2.1.2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] Applying patches to local machine

[Christian Kellermann]

[-- Attachment #1: Type: text/plain, Size: 559 bytes --]

* Charles Forsyth <forsyth@terzarima.net> [071102 11:22]:
> see http://plan9.bell-labs.com/wiki/plan9/Staying_up_to_date/index.html

I think I should clarify my question: Is there a way to use the
patch/* utilities as a non developer to apply patches in
/n/sources/patch to my local machine? If not how can I do this
easily without copying all files manually?

I was not referring to updating my system.

Thanks for your answer,

Christian

-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] Applying patches to local machine

[Anthony Sorace]

I think he's asking whether there's any way to apply not yet
integrated/approved patches to his local source.

It looks like running patch/apply works for everyone, modifying
whatever the local root is (rather than explicitly working on
/n/sources), which is nice. It does require you having write
permissions on (its view of) the patch directory itself:

	:; patch/apply savec/cpu-cec
	.tmp: rc (apply): can't open: '.tmp' permission denied
	:; ramfs && bind -bc /tmp /n/sources/patch/saved/cpu-cec
	:; patch/apply saved/cpu-cec
	merge...backup...cp: can't stat /sys/src/9/port/devcec.c:
'/sys/src/9/port/devcec.c' does not exist
copy...
	to update sources:
		update /sys/src/9/port/portfns.h
		update /sys/src/9/port/devcec.c
		update /sys/src/9/port/devcons.c

That cp error after backup is just because devcec.c isn't an existing
file in the system. I'm not sure whether those update lines are
intended to be executable commands we just don't have (looks like) or
advisory, but either way your local tree is now updated.

This is neat, by the way. I'd never thought to actually check if this
worked or not. Given it's this easy, I think I'll play around with the
rio pie menu stuff. Thanks!

Anthony

Re: [9fans] Applying patches to local machine

[Christian Kellermann]

[-- Attachment #1: Type: text/plain, Size: 391 bytes --]

* Anthony Sorace <anothy@gmail.com> [071102 11:41]:

> This is neat, by the way. I'd never thought to actually check if this
> worked or not. Given it's this easy, I think I'll play around with the
> rio pie menu stuff. Thanks!

This is the reason I asked :)

Thanks Anthony!

-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] Applying patches to local machine

[Christian Kellermann]

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

Hi,

the above suggestion does not work for me, the merging cannot copy
files due to permission problems. I haven't looked further into the
issue yet. This happens when running commands not intended for this
purpose :)


-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] Applying patches to local machine

[Anthony Sorace]

all the /bin/patch/* files are just shell scripts, so it's easy to see
what's going on. which stage gives you permission errors? in a default
setup, you'll have to be in group sys, as that's who owns all the
sources.

if you can't be in sys for whatever reason, you'll have a somewhat
more manual process ahead of you. identify the files to be modified,
create local copies (i'm assuming you can at least *read* them,
otherwise this is probably futile), bind them over the system ones,
and re-run the patch command.

of course, i'm largely guessing without an error message.

Re: [9fans] Applying patches to local machine

[erik quanstrom]

> all the /bin/patch/* files are just shell scripts, so it's easy to see
> what's going on. which stage gives you permission errors? in a default
> setup, you'll have to be in group sys, as that's who owns all the
> sources.
> 
> if you can't be in sys for whatever reason, you'll have a somewhat
> more manual process ahead of you. identify the files to be modified,
> create local copies (i'm assuming you can at least *read* them,
> otherwise this is probably futile), bind them over the system ones,
> and re-run the patch command.
> 
> of course, i'm largely guessing without an error message.

read the source, luke.

patch/apply assumes you are at bell labs with appropriate permissions
to /n/sources.  the script bails if you can't touch files in the patch's
directory.

it is also likely that you'll need to merge the source by hand as
the piemenu patch is very old.

you likely want to make a seperate copy of libdraw and link against
it selectivly by binding the archive on /386/lib/libdraw.a

- erik

Re: [9fans] Applying patches to local machine

[Dave Eckhardt]

> if you can't be in sys for whatever reason, you'll have a somewhat
> more manual process ahead of you. identify the files to be modified,
> create local copies (i'm assuming you can at least *read* them,
> otherwise this is probably futile), bind them over the system ones,
> and re-run the patch command.

Don't forget about divergefs(*)... "divergefs -p /some/dir /sys" will
let you virtually write all over /sys, including deleting files, and
will also let you resume that environment later.

Dave Eckhardt

(*) Some compilation required.