Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Jul 2018 19:51:26 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 230114] [NEW PORT] textproc/scancode-toolkit: Scans code for license, copyright, package and documented dependencies
Message-ID:  <bug-230114-21822-krkojj2CHh@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-230114-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-230114-21822@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230114

--- Comment #5 from Nathan <ndowens.fbsd@yandex.com> ---
(In reply to Kai from comment #4)
> (In reply to Nathan from comment #1)
> (In reply to Nathan from comment #3)
>=20
> It depends in which context you do apply the patch. If you do e.g.
>=20
> > $ cd /path/to/your/ports/tree
> > $ svn patch --dry-run ~/scancode-toolkit.patch textproc/
>=20
> from the root of your svn tree, you should get a similar output like belo=
w:
>=20
> > A         textproc/scancode-toolkit
> > A         textproc/scancode-toolkit/Makefile
> > A         textproc/scancode-toolkit/distinfo
> > A         textproc/scancode-toolkit/files
> > A         textproc/scancode-toolkit/files/patch-setup.py
> > A         textproc/scancode-toolkit/files/patch-src_commoncode_system.py
> > A         textproc/scancode-toolkit/pkg-descr
>=20
> The same result you would get with:
>=20
> > $ cd /path/to/your/ports/tree
> > $ cd textproc
> > $ svn patch --dry-run ~/scancode-toolkit.patch
>=20
> The output would be:
>=20
> > A         scancode-toolkit
> > A         scancode-toolkit/Makefile
> > A         scancode-toolkit/distinfo
> > A         scancode-toolkit/files
> > A         scancode-toolkit/files/patch-setup.py
> > A         scancode-toolkit/files/patch-src_commoncode_system.py
> > A         scancode-toolkit/pkg-descr
>=20
> When applying your patch with the "corrected" paths the output will show
> some differences which yields into a non functional port that cannot be
> built:
>=20
> > $ cd /path/to/your/ports/tree
> > $ svn patch --dry-run ~/corrected_paths.patch textproc/
> > A         textproc/textproc
> > A         textproc/textproc/scancode-toolkit
> > A         textproc/textproc/scancode-toolkit/Makefile
> > A         textproc/scancode-toolkit
> > A         textproc/scancode-toolkit/distinfo
> > A         textproc/scancode-toolkit/files
> > A         textproc/scancode-toolkit/files/patch-setup.py
> > A         textproc/scancode-toolkit/files/patch-src_commoncode_system.py
> > A         textproc/scancode-toolkit/pkg-descr
>=20
> As for the info about the non-existent origins - have you updated your po=
rts
> tree? Your ports tree needs to be at least at r475546 to have all the por=
ts
> that are required to build textproc/scancode-toolkit successfully.

https://www.freebsd.org/doc/en/books/porters-handbook/book.html#porting-sub=
mitting
Example 3.1. Creating a .diff for a New Port

Add all the files with svn add. cd to the base of the ports tree so full pa=
ths
to the changed files are included in the diff, then generate the diff with =
svn
diff. For example:

% svn add .
% cd ../..
% svn diff games/oneko > oneko.diff

Important:

To make it easier for committers to apply the patch on their working copy of
the ports tree, please generate the .diff from the base of your ports tree.


Updated ports tree and finally seems it found deps needed

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230114-21822-krkojj2CHh>