Date: Mon, 3 May 2010 23:01:27 +0300 From: Ion-Mihai Tetcu <itetcu@FreeBSD.org> To: Rene Ladan <r.c.ladan@gmail.com> Cc: ports@freebsd.org, Garrett Cooper <yanefbsd@gmail.com> Subject: Re: Dixit port bad management Message-ID: <20100503230127.58979b9f@it.buh.tecnik93.com> In-Reply-To: <4BDF1F8D.4090401@gmail.com> References: <COL105-W64A7586A8A88F0FC9457A9C8F10@phx.gbl> <v2u7d6fde3d1005031200y5e5243b5yb3b566d2a26a1b21@mail.gmail.com> <4BDF1F8D.4090401@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/EkbVQZ2e4sp1S34yHnA+UkV
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
On Mon, 03 May 2010 21:10:05 +0200
Rene Ladan <r.c.ladan@gmail.com> wrote:
> On 03-05-2010 21:00, Garrett Cooper wrote:
> > On Sun, May 2, 2010 at 12:59 PM, Tim A <cxtim@live.com> wrote:
> >>
> >> 1) I don't understand why the Textproc/Dixit port is so badly
> >> managed. The program itself is at version 10.4, while your
> >> unprofessional port still stays at version 1.0.1, claiming that
> >> the GCC 4.2 compilation is broken.
> >>
> >> 2) I don't understand either why you don't use Dixit sourceforge
> >> RSS feeds to know when a new version is available.
> >>
> >> 3) I don't understand how your Dixit port points to files which
> >> don't exist anymore.
> >>
> >> 4) I don't understand the suprematism attitude of the maintainers
> >> in charge, who don't give a penny on the programs they are suppose
> >> to maintain. They are only interested in the statistics generated
> >> by their unprofessional ports, but not in their quality.
> >=20
> > Tim,
> >=20
> > Here's a start. I'll leave it as an exercise for you to fix the rest
> > of the bits; I at least got you past the fun sites change in the
> > extract part, but the path for ${_DB_D} with what's setup in the
> > Makefile differs from reality (the current path is:
> > ${SOURCEFORGE_SITE}/project/dixit/dixit_qdb/dixit.qdb.tar.bz2 , not
> > ${SOURCEFORGE_SITE}/project/dixit/dixit/10.4/dixit.qdb.tar.bz2 );
> > you probably don't want to pull the potentially out-of-sync zip
> > file from ftp*.freebsd.org , especially because we can decompress a
> > tarball natively without installing archivers/unzip .
> >=20
> > I've trimmed out a lot of the fud, but you'll probably have to do
> > some hacking to get the project to work with QT3 or QT4 (hopefully
> > the latter).
> >=20
> > The porter's handbook [1] is your guide as well as make(1) [2].
> >=20
> > After that, run `make makesum all install ' . Submit a PR with the
> > diffs for all of the files if it works to your liking.
> >=20
> Before running 'make install', run 'port test' to see if the port is
> nicely formatted and that the package contents is correct, meaning it
> doesn't leave files behind on uninstall or tries to uninstall files
> which don't exist.
Blah, don't loose the time on this. You won't get any PR anyway.
I committed an update to the port, which almost works in this version
(except the menus, and that might be a question of fonts/locale).
Then tomorrow I'll nicely drop maintainership and schedule it for
deletion, no body being interested in it and me being so unprofessional.
Damn, there goes my record!
--=20
IOnut - Un^d^dregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B
--Sig_/EkbVQZ2e4sp1S34yHnA+UkV
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
iEYEARECAAYFAkvfK5gACgkQJ7GIuiH/oeUPvACfam6rbtRaSTWFnuuMz22RRfFV
mRkAniH4U2wBBpWLrsLcfhM9rRRQ+HVi
=ThQi
-----END PGP SIGNATURE-----
--Sig_/EkbVQZ2e4sp1S34yHnA+UkV--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100503230127.58979b9f>