Hi Matthias,
Thank you for the email and your efforts. I have no problem with anything. Otherwise, your logic is wrong. At least one person was interested. Best, Tim > Subject: Fwd: Re: Dixit port bad management > To: cx...@live.com > Date: Tue, 4 May 2010 09:36:33 +0200 > From: matthias.and...@gmx.de > > Hi Tim, > > I am writing this just so the announcement doesn't get lost and double > effort is wasted... please see below, unless you've seen it on the list > already. For further discussion, please continue using the > po...@freebsd.org mailing list. > > HTH > Matthias > (mand...@freebsd.org) > > ------- Weitergeleitete Nachricht ------- > Von: "Ion-Mihai Tetcu" <ite...@freebsd.org> > An: "Rene Ladan" <r.c.la...@gmail.com> > Kopie: po...@freebsd.org, "Garrett Cooper" <yanef...@gmail.com> > Betreff: Re: Dixit port bad management > Datum: Mon, 03 May 2010 22:01:27 +0200 > > On Mon, 03 May 2010 21:10:05 +0200 > Rene Ladan <r.c.la...@gmail.com> wrote: > > > On 03-05-2010 21:00, Garrett Cooper wrote: > > > On Sun, May 2, 2010 at 12:59 PM, Tim A <cx...@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. > > > > > > Tim, > > > > > > 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 . > > > > > > 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). > > > > > > The porter's handbook [1] is your guide as well as make(1) [2]. > > > > > > After that, run `make makesum all install ' . Submit a PR with the > > > diffs for all of the files if it works to your liking. > > > > > 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! > > > -- > Matthias Andree _________________________________________________________________ MSN Dating: Find someone special. Start now. http://go.microsoft.com/?linkid=9729707_______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"