Date: Fri, 12 May 2000 09:00:05 +0200 From: Stijn Hoop <stijn@win.tue.nl> To: freebsd-ports@freebsd.org Subject: Re: How to submit port updates (Re: ports/18502: Mutt is now at 1.2) Message-ID: <20000512090005.B86084@pcwin002.win.tue.nl> In-Reply-To: <001c01bfbbab$96840760$8dfee0d1@westbend.net>; from hetzels@westbend.net on Thu, May 11, 2000 at 07:46:47PM -0500 References: <200005120005.RAA84611@tao.thought.org> <001c01bfbbab$96840760$8dfee0d1@westbend.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Patrick Seal sugested another way to insert the patch. I have amended the
> procedure as follows:
>
> > > 1. Make a copy of the original port (muuz)
> > >
> > > cp -rp muuz muuz.orig
> > >
> > > 2. Make changes to port (muuz)
> > >
> > > 3. Create a diff between the original and the changed version.
> > >
> > > diff -ruN muuz.orig muuz > muuz.patch
> > >
> > > 4. Use send-pr to create Problem Report
> > >
>
> 5. Move to the end of the PR (after 'Fix:') and insert your patch (vi
> command) (As sugested by Patrick Seal)
>
> :r muuz.patch
>
> 6. Quit out of the editor (vi), you'll then be asked to send, edit or abort
> the PR.
>
> > >
> > > 9. Use send to submit your PR
> > >
> > > There's probably an easier way to generate and submit the PR, but I am
> not
> > > sure what the vi command is to insert text from a file.
> > >
> >
> > Thank you; this fits exactly:: a cookbook-style howto. Once
> > I've done this procedure a few times the edges (reasons, whys,
> > and wherefores) will become clear.
> >
> Scot
Could this procedure be added to the new porter's handbook?
--Stijn
--
FreeBSD: | Death is life's way of telling you you've been fired.
The power to serve | -- R. Geis
www.freebsd.org |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000512090005.B86084>