Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Jul 2014 20:16:43 +0200
From:      Roland Smith <rsmith@xs4all.nl>
To:        Tim Daneliuk <tundra@tundraware.com>
Cc:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: Need Complete Idiots Guide To Fixing My Ports
Message-ID:  <20140707181643.GA43724@slackbox.erewhon.home>
In-Reply-To: <53BAAEB8.2040502@tundraware.com>
References:  <53BAAEB8.2040502@tundraware.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 07, 2014 at 09:29:12AM -0500, Tim Daneliuk wrote:
> So the portmaster is nagging me to update my ports to the newfangled ports
> system.  I  glanced at the docs and it looks like way more effort than I
> want to put into it.  I have REALLY simple ports of things like python
> programs and their docs.
>=20
> Is there some simple, 4 step process I can apply to my ports without havi=
ng
> to resort to testing with poudriere and the like?  (Because I won't bothe=
r,
> I'll just quit supporting the FreeBSD ports model and release stuff
> on my own website ...)

1) Read https://wiki.freebsd.org/ports/StageDir, /usr/ports/Mk/bsd.python.m=
k,
   porters handbook
2) Start with a new empty Makefile, to get rid of all the cruft.
3) Re-write the Makefile with the above references and other Python ports t=
hat
were already fixed. If you're not changing a version, you can keep the dist=
info.
If you are using distutils, you might not even have to write a pkg-plist.
4) Run `env DEVELOPER=3Dyes make stage && make check-plist && make package`=
 *as
a normal user* and portlint on your new port to test.

I've got some patches for Python-based ports in the queue it you want to ha=
ve a look at
them;
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191103
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D190674

Possibly 190674 is a-typical because this software has a Makefile instead o=
f a
setup.py. This is because I'm combining the script and its dedicated module=
s into
a single zip-file for convenience.

Roland
--=20
R.F.Smith                                   http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 5753 3324 1661 B0FE 8D93  FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)

--r5Pyd7+fXNt84Ff3
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJTuuQLAAoJEED21dyjijPgVWMQALmCoLUJqLf0bNBwl1mZ+mVW
C6qxy6QE7A+4vBzGmSAmJfJY7QTedoyz/b356MW7g00k7GK7mg/cFLT/LVqp2Rl3
BFDipVvTvyOXItAhVmrRV2fzzwHZoK9v4DnZoYvXUR8tSYmAd0JPDUGlHc7yXE6V
EDz+wBvC0s0QxWmEFay3LZu3pTsSnsEGsDw4UlIa94+XBD3GlZkTM2BlYZyypXxp
oD1F3uhAquVUWFQ1qw0IEr1aNWkklntvWvuJ9I9fY9d9jjSRRrLMz1qxGdbpqOgW
N61HNZUnzo6Oueq0oeWyKWWED/clqIKhZk71RcizNCxXazpVVh2HHp/YiSXPf4zB
yk/gUnoPgK0CoFtJbWYMo1/EB7yzpAzf9TvPokBLERg9VHFR7IiOcWzpUKi3sSZ7
R2rebX4XMtZc3A3U44c981dou+oz3aOXWqnaaLlo9UnNzrA74RLk/gdLxEBnbgID
C9hIDABHzRfx0jjk5LUunGaskF6CQ8th8z2tK7qovBmkbuuFutvnA2EQgyroYQ9b
DzxVrBek7FpjoAghqgwjEsTwHTzDdw0GHOqEYlEbW+nTr+VUvX3tUnGSUnhcPB40
fkTuKZmudxP34O7d0Q0IBj2pc+ZAAd8cGG+PpsNAC9PHureeuW2vd3cj/lJON7V9
eJVVFEgvgRQsDlBozfqI
=3XmO
-----END PGP SIGNATURE-----

--r5Pyd7+fXNt84Ff3--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140707181643.GA43724>