[ic] products dir / config dir / intuitive?

[Mark Johnson]

They are just letters. ProductDir could be 'asdfouuhEFDouhd' and it
would make no difference. The point is, if you want the thingies that
are currently in products/ to be in config/, the directive that
identifies those thingies is called ProductDir. So, if to YOU, it makes
more sense to have those thingies in config/, then that's how you do it.

Do you also propose that HTTP_REFERER begin to be spelled properly just
because it doesn't make sense in English? The fact is, once something
becomes a convention, and the longer that convention is held, the harder
it is to justify changing it, and the more stuff you get to break if you
do have to change it.

Jud Harris wrote:
> 
> .. well, it seems that doing what you suggested only pushes the inconsitency
> one level lower.
> 
> Adding "ProductDir    config" is like saying, "Let's call the directory in
> which we store product data 'config'
> 
> Instead, something like...
> 
> ---
> ConfigDir     config
> ProductDir    products
> ---
> 
> ... seems to make better sense.
> 
> But then again, maybe I'm just way too anal about this?  Anyone else have
> any thoughts?
> 
> -Jud
> 
> ----- Original Message -----
> From: "Mark Johnson" <markj@redhat.com>
> To: <interchange-users@developer.akopia.com>
> Sent: Wednesday, July 11, 2001 3:09 PM
> Subject: Re: [ic] products dir / config dir / intuitive?
> 
> > Add
> >
> > ProductDir     config
> >
> > to your catalog.cfg, and in the current and all future releases (for
> > you), that will be your data repository.
> >
> > Personally, I use config for any normally global variables that I wish
> > to override for a specific catalog. It's all what you are (or get) used
> > to.
> >
> > Jud Harris wrote:
> > >
> > > Hey gang,
> > >
> > > Is seems odd to me that the "products" directory in each catalog dir is
> > > named "products" - when, if fact, few of the *config* files in it
> pertain
> > > directly to products.  It's counter-intuitive if you ask me.
> Additionally,
> > > the "config" directory doesn't do too much config.  I've never touched
> it
> > > over the course of many catalog setups.
> > >
> > > Does it not make more sense to move the config-type files from products
> into
> > > the config dir for future releases?  If not, why not?
> > >
> > > Just curious,
> > > -Jud
> > >
> > > _______________________________________________
> > > Interchange-users mailing list
> > > Interchange-users@lists.akopia.com
> > > http://lists.akopia.com/mailman/listinfo/interchange-users
> >
> > --
> > Mark Johnson
> > Senior Systems Architect - Professional Services
> > Red Hat, Inc.
> > E-Business Solutions
> > markj@redhat.com
> > 703-456-2912
> > _______________________________________________
> > Interchange-users mailing list
> > Interchange-users@lists.akopia.com
> > http://lists.akopia.com/mailman/listinfo/interchange-users
> >
> 
> _______________________________________________
> Interchange-users mailing list
> Interchange-users@lists.akopia.com
> http://lists.akopia.com/mailman/listinfo/interchange-users

-- 
Mark Johnson
Senior Systems Architect - Professional Services
Red Hat, Inc.
E-Business Solutions
markj@redhat.com
703-456-2912