Miroslav Lachman wrote on 2018/12/04 12:44:
I am trying to create patch for pandorafms_console to make it work with
PHP 7.1. There are 5 file that need to be patched. I created *.orig for
all of them, make changes in them and then "make makepatch" created
patches only for 2 out
I am trying to create patch for pandorafms_console to make it work with
PHP 7.1. There are 5 file that need to be patched. I created *.orig for
all of them, make changes in them and then "make makepatch" created
patches only for 2 out of 5 files.
Patches are crated for:
install.p
On Thu, Oct 27, 2016 at 2:28 AM, Jochen Neumeister <jon...@bsdproject.de> wrote:
>
>
> On 27.10.2016 08:08, Franco Fichtner wrote:
>>> On 27 Oct 2016, at 7:53 AM, Jochen Neumeister <jon...@bsdproject.de> wrote:
>>>
>>> N
> On 27 Oct 2016, at 04:20, Kurt Jaeger <li...@opsec.eu> wrote:
>
> Hi!
>
>> # portlint
>> WARN: /usr/home/joneum/dev/ports/net/wpa_gui/files/patch-wpa_ctrl.c:
>> patch was not generated using ``make makepatch''. It is recommended to
>> use ``make
ps://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
Here, the procedure that I use to make patches is the follow.
If a previously patch to file that need be edited exists in files dir
# make patch
// do
> On 27 Oct 2016, at 8:28 AM, Jochen Neumeister wrote:
>
> Is this now right, that i can only use the new patch in /files? With
> "make clean" i delete the work folder and the old patches.
If all the previous patches patch a single file, makepatch will generate the
patch
On 27.10.2016 08:08, Franco Fichtner wrote:
>> On 27 Oct 2016, at 7:53 AM, Jochen Neumeister <jon...@bsdproject.de> wrote:
>>
>> No, make makepatch delete the patches into /files and:
> If there are no patches in files/ maybe you have no patches applied
> in the
On Thu, Oct 27, 2016 at 07:47:06AM +0200, Jochen Neumeister wrote:
Hello Jochen!
> I will update the net/wpa_gui.
>
> # portlint
> WARN: /usr/home/joneum/dev/ports/net/wpa_gui/files/patch-wpa_ctrl.c:
> patch was not generated using ``make makepatch''. It is recommended
Hi!
> # portlint
> WARN: /usr/home/joneum/dev/ports/net/wpa_gui/files/patch-wpa_ctrl.c:
> patch was not generated using ``make makepatch''. It is recommended to
> use ``make makepatch'' when you need to [re-]generate a patch to ensure
> proper patch format.
> 0 fatal errors a
> On 27 Oct 2016, at 7:53 AM, Jochen Neumeister <jon...@bsdproject.de> wrote:
>
> No, make makepatch delete the patches into /files and:
If there are no patches in files/ maybe you have no patches applied
in the work/ dir? Does running "make patch" before makepat
On 27.10.2016 07:50, Franco Fichtner wrote:
> Hi Jochen,
>
>> On 27 Oct 2016, at 7:47 AM, Jochen Neumeister <jon...@bsdproject.de> wrote:
>>
>> what am i doing wrong?
> Doesn't makepatch already place the new patches in files/?
>
No, make makepatch delete t
Hi Jochen,
> On 27 Oct 2016, at 7:47 AM, Jochen Neumeister wrote:
>
> what am i doing wrong?
Doesn't makepatch already place the new patches in files/?
Cheers,
Franco
___
freebsd-ports@freebsd.org mailing list
I will update the net/wpa_gui.
# portlint
WARN: /usr/home/joneum/dev/ports/net/wpa_gui/files/patch-wpa_ctrl.c:
patch was not generated using ``make makepatch''. It is recommended to
use ``make makepatch'' when you need to [re-]generate a patch to ensure
proper patch format.
0 fatal errors and 1
to worry about the patch order: hunks are
grouped by-file, so any patch order will go;
- one can simply invoke 'make makepatch' to produce all patchfiles
automatically after the virgin sources were patched and .orig
files were left in place.
There is the third reason from the Porters
14 matches
Mail list logo