Re: [mv] Undefined catalog:

[cfm@maine.com]

******    message to minivend-users from cfm@maine.com     ******

On Sat, Apr 01, 2000 at 12:09:32PM +0200, Stefan Hornburg wrote:
> ******    message to minivend-users from Stefan Hornburg <racke@linuxia.de>     ******
> 
> Mike Heins <mikeh@minivend.com> writes:
> 
> > ******    message to minivend-users from Mike Heins <mikeh@minivend.com>     ******
> > 
> > Quoting Bill Randle (billr@exgate.tek.com):
> > > As a side note: Mike, have you thought about using (or are you using) a bug
> > > tracking system of any kind? I know there are several packages out
> > > there to do this. An always uptodate web page could be built from the
> > > bug db if you didn't want to make the bug db itself available for read
> > > access. If you're interested in something like this, let me know offline
> > > and I'll do a current check and give you feedback and [my] suggestions
> > > (it's been awhile since I looked at this).
> > > 

I wonder if that makes sense for minivend.  Most of the difficulties
seem to be **system** and installation related.  I'd sure hate to see
bugs filed against documentation, incompatibilities, "why won't it work",
or even installation, etc....  Those will never get solved satisfactorily.
I'd guess that a bug system would mean users filing bugs and sitting
back, complaining that they filed a bug and it hasn't been fixed yet
when the real issue is not minivend.

If someone doesn't understand web server, permissions, paths and so
on and their installation fails, it's not a minivend bug.  Rather,
if it succeeds under those conditions it is instead a minivend MIRACLE.

We recently ran into an (issue|bug) with minivend, Roxen and tlink. tlink
was passing args to minivend running on a WN server, but the arguments
had been "pre-decoded" by Roxen.  Roxen and WN did not quite agree on
what to do with space/+/%20.  A process with "Browse Catalog" that worked on
either machine did not work over network via tlink.

I don't know if that is a bug in minivend, WN, Roxen or tlink.  My bet
is that it is a conceptual flaw in tlink, but one that will only bite
the millions of systems mixing Roxen and WN servers.  ;^)

That being said, some sort of a minivend-bug.pl script like that used
for mysql or emacs would probably be a good idea.  It would describe
system, users, permissions, installation, and how the user can duplicate 
the problem or it is not a bug.  Perhaps a separate mailing list, rather
than a web page would be less work?

cfm


-- 

Christopher F. Miller, Publisher                             cfm@maine.com
MaineStreet Communications, Inc         208 Portland Road, Gray, ME  04039
1.207.657.5078                                       http://www.maine.com/
Database publishing, e-commerce, office/internet integration, Debian linux.
-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list