make makepatch
Otacílio de Araújo Ramos Neto
otacilio.neto at bsd.com.br
Thu Oct 27 08:33:24 UTC 2016
Em qui, 27 de out de 2016 03:31, Franco Fichtner <franco at lastsummer.de>
escreveu:
>
> > On 27 Oct 2016, at 8:28 AM, Jochen Neumeister <joneum at bsdproject.de>
> 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 for the file, because it doesn't care about the ptch context, just
> the
> file.
>
> If you want, you can deconstruct the new patch file and push the individual
> chunks into their old files to silence portlint, but that only works if the
> patches do not depend on each other.
>
>
> Cheers,
> Franco
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at 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 my modificativos
#make makepatch
If a previously patch to file that need be edited do not exists in files dir
# make patch // to extracto and apply patches to others files
# cp work/blabla/file wor/blabla/file.orig
// do my modificativos
# make makepatch
So, a New patch is created in files dir
In a hope that can help
[]'s
-Otacilio
>
More information about the freebsd-ports
mailing list