[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: csound: plugin path problem



On Fri, 2008-02-01 at 12:07 -0500, Michel Salim wrote:
> On Feb 1, 2008 6:51 AM, Dan Williams <dcbw redhat com> wrote:
> > On Fri, 2008-02-01 at 01:00 -0500, Michel Salim wrote:
> > > The problem was reported in  bugzilla entry
> > > https://bugzilla.redhat.com/show_bug.cgi?id=407911 in December, and
> > > there has been two duplicate bug reports since (one is mine, both now
> > > merged).
> >
> > I'm not necessarily sure the manual and tutorial should depend on csound
> > itself; there isn't really any run-time or build-time dependency on
> > csound.  The only issue would be if you updated csound to a new version
> > but the manual or tutorials were still the old version.  Thoughts?  Do
> > you really want to have to download all 3MB of the manual every time a
> > new build of csound hits the repos?
> >
> If they come from the same source package, then you'd have a newer
> version of the manual and tutorial sitting on the server anyway, so
> users who 'yum update' would get it?
> 
> One way to let users who insist on not updating the documentation
> would be to make them Requires: csound = N-V without the release
> component. Not sure that's recommended though.
> 
> PS there are some really old csound bugs in Bugzilla. Not sure some
> are still relevant (from 2006). How we used to live before PKGDB
> provided easy access to package-specific bugs...

That's what I'm trying to clean up; except that F-8 build repos are
broken (tk-devel depends on a newer tcl-devel version than is present in
F-8 repos) and F-9 is broken (pdflatex can't find some config files).
Whee.

Dan



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]