Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Jan 2000 11:33:37 -0600
From:      Karl Denninger <karl@Denninger.Net>
To:        Steve Price <sprice@hiwaay.net>, freebsd-ports@FreeBSD.ORG
Subject:   Re: ports/15822: Update port misc/HomeDaemon to V0.99
Message-ID:  <20000101113337.A89903@Denninger.Net>
In-Reply-To: <200001011710.JAA08349@freefall.freebsd.org>; from Steve Price on Sat, Jan 01, 2000 at 09:10:02AM -0800
References:  <200001011710.JAA08349@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 01, 2000 at 09:10:02AM -0800, Steve Price wrote:
> The following reply was made to PR ports/15822; it has been noted by GNATS.
> 
> From: Steve Price <sprice@hiwaay.net>
> To: Karl Denninger <karl@Denninger.Net>
> Cc: FreeBSD-gnats-submit@FreeBSD.ORG
> Subject: Re: ports/15822: Update port misc/HomeDaemon to V0.99
> Date: Sat, 1 Jan 2000 10:53:56 -0600 (CST)
> 
>  On Sat, 1 Jan 2000, Karl Denninger wrote:
>  
>  # >Number:         15822
>  # >Category:       ports
>  # >Synopsis:       Update port misc/HomeDaemon to V0.99
>  [snip]
>  # 	(Please note that I still don't see this port in the CVS tree,
>  # 	although I DID see the "committed, thanks!" note on the original
>  # 	submission a few days back!  Please check this - thank you)
>  
>  Karl,
>  
>  You didn't see the "committed, thanks!" note on any of your PRs.

Correct.  My first submission got a reject and nasty comment back from 
one of your other committers that I violated the hier(7) rules - when I 
explained why I had done so, I got stony silence in reply.

So I went back to the code and did a LOT of work to conform and write
installation code - even though it probably wasn't such a good idea,
as I found out later, in that doing so (and doing the PLIST and other
stuff "the FreeBSD way") made it really easy to LOSE a *LOT* of hard
work for the users of the software.

Guess how *I* found out about that little pitfall?  Yeah.  Good thing
I have an automatic nightly tape backup run.  Two hours later after
waiting for the tape to read through, I had my event file back.  :-(

So today I submitted a port with those PLIST entries DELETED (intentionally)
which ALSO violates the rules in the handbook, but I'll be damned if blind 
complience with "the rules" supersedes the principle of least astonishment 
(and the 4-letter words that will eminate from someone who does not have a 
backup after they spend all weekend programming an event list only to lose 
it due to this!)

>  So far I have closed three other PRs regarding your new HomeDaemon
>  software, ports/{15749,15772,15773}.  If you'd check the audit trail
>  of these you'll see they say "superceded by ports/...".  This is
>  why you haven't seen it in the CVS tree.  You keep sending in new
>  submissions for the same port before someone can commit the old one. :)

Uh, not quite.

The original was never committed because someone else (not you) has 
refused to do so.  You closed the others which is fine, but none of the
originals was ever committed, and in fact, since the first REJECT message
I had no idea if you folks were *ever* going to commit the original - and
had assumed the answer was *no*.

I'll be happy to wait, but when someone tells me to go stuff, basically,
and then does not reply to my follow-up in a timely fashion (a couple
of days) I have only two options:

	1. Assume that someone was having a bad day, closed the original,
	   and I should resubmit.

	2. Give up.

I assume you'd prefer that I *not* take path #2.

>  Two quick things...
>  
>  Please don't create a new PR everytime you want to follow up to
>  an old one.  The proper procedure is to send a message like this:
>  
>  	From: Karl Denninger <karl@Denninger.Net>
>  	To: freebsd-gnats-submit@freebsd.org
>  	Subject: Re: ports/15882
>  
>  	...

I thought send-pr was the way to "talk to" gnats officially... If not, ok,
but then the original has to be comitted first before I can do this (as you
noted below).

>  Secondly if this were an update to an existing port, please send
>  us a diff from the current port and not a new shar file.  In this
>  case since there is no current port you really had no choice but
>  to send a new shar file.  Just so you know... :)
>  
>  Thanks.
>  
>  -steve

See above.

Any idea on a timeline when the "now original" commit can/will be done?

--
-- 
Karl Denninger (karl@denninger.net)  Web: http://childrens-justice.org
Isn't it time we started putting KIDS first?  See the above URL for
a plan to do exactly that!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




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