On Sun, 5 Jul 2020 13:07:53 +1200 Jonathan Chen j...@chen.org.nz said
On Sun, 5 Jul 2020 at 12:47, Brandon helsley
wrote:
>
> I have gotten a couple of emails from portscout about ports that need updated
> and maintained. Before I go about updating and maintaining these ports I
wanted
> to do
On Sun, 5 Jul 2020 00:46:39 + Brandon helsley brandon.hels...@hotmail.com
said
I have gotten a couple of emails from portscout about ports that need updated
and maintained. Before I go about updating and maintaining these ports I
wanted to do some practice on a couple that I use like
# svn diff sysutils/toybox > /home/vidar/portdiffs/sysutils_toybox-0.8.4.diff
Yes the whole message cleared it up. But right here now I see
/home/vidar/portdiffs/sysutils_toybox-0.8.4.diff is where you keep the diff
before submiting it.
>
> On Jul
> On 5 Jul 2020, at 16:42, Brandon helsley wrote:
>
>> For making changes to a port, I find ’svn diff’ to be the easiest way by
>> far. I tend to do this:
>> 1. svn up my work-in-progress ports tree
>> 2. Make the changes and run tests (portlint, poudriere testport etc)
>> 3. cd /ports; svn
eebsd-po...@freebsd.org] on
behalf of Vidar Karlsen [vi...@karlsen.tech]
Sent: Sunday, July 5, 2020 2:18 AM
To: Brandon helsley
Cc: freebsd-ports
Subject: Re: Porting Practice
> On 5 Jul 2020, at 02:46, Brandon helsley wrote:
[…]
> The documentation for (diff -u) says "To create a suitabl
p when I am supposed
to... get the port working in my working directory I get stuck.
From: Jonathan Chen [j...@chen.org.nz]
Sent: Saturday, July 4, 2020 7:07 PM
To: Brandon helsley
Cc: freebsd-ports
Subject: Re: Porting Practice
On Sun, 5 Jul 2020 at 12
> On 5 Jul 2020, at 02:46, Brandon helsley wrote:
[…]
> The documentation for (diff -u) says "To create a suitable diff for a single
> patch, copy the file that needs patching to something.orig, save the changes
> to something and then create the patch:"
> % diff -u something.orig something
Please be aware that this port is maintained by x...@freebsd.org and anyone
who is subscribed to the x11 mailing list will get the portscout messaged.
This does not mean it is intended that aloof those who subscribe to x11 are
responsible for making repaired.
If you have not done so, check
On Sun, 5 Jul 2020 at 14:06, Brandon helsley
wrote:
[...]
>
> Yes it does, I understand how it works now, I just needed an example, and I
> can compare this with other methods to figure it out. How do you get the port
> working in your directory?
In general:
1. extract the original sources
This is my personal workflow:
1. Take a simple copy of the port into my working directory
2. Get the port working in my working directory.
3. cd my-working-directory
4. diff -ruN /usr/ports/x11/nvidia-settings . > /tmp/nvidia-settings.patch
5. submit patch onto
On Sun, 5 Jul 2020 at 12:47, Brandon helsley
wrote:
>
> I have gotten a couple of emails from portscout about ports that need updated
> and maintained. Before I go about updating and maintaining these ports I
> wanted to do some practice on a couple that I use like x11/nvidia-settings. I
>
I have gotten a couple of emails from portscout about ports that need updated
and maintained. Before I go about updating and maintaining these ports I wanted
to do some practice on a couple that I use like x11/nvidia-settings. I have
recieved alot of help on the forums and from the
12 matches
Mail list logo
