Re: PROPOSAL: /opt/<provider>/<package>/]

Also, what exactly qualifies a <package>?  For instance, we
have one application that is split into about 10 RPMs, all
of which are required to be installed.  I'm not sure why they
have that level of granularity, but I've seen this with other
applications as well (ApplixWare).  Does <package> have
to correspond to an RPM name?

On Friday 30 May 2003 04:05 am, Gerhard Muntingh wrote:
> On Thu, May 29, 2003 at 11:51:24AM -0600, Bart Whiteley wrote:
> > Also, I would prefer that configuration data be allowed to
> > be in /etc/opt/<provider>/<something>, where <something>
> > does not necessarily correspond to a "package".  Similar
> > arguments apply here.  Perhaps there are some configuration
> > files that are used by a lot of "packages".
>
> Why not a configuration package?
>
> > This fourth rule covers init and cron scripts, as well as other
> > things not currently covered in the specification (like
> > /etc/logrotate.d/<provider>-*).
>
> I think logrotate should be patched to use /etc/opt/logrotate.d/ also
> if it exists.  And ofcourse the same for cron and init.
>
>
> Just thought,
>
> Gerhard.

-- 
Bart Whiteley <[email protected]>
Novell, Inc.  The leading provider of information solutions. 
http://www.novell.com/