Skip to Content.
Sympa Menu

sm-sorcery - Re: [SM-Sorcery] splitting BUILD

sm-sorcery AT lists.ibiblio.org

Subject: Discussion of Sorcery related topics

List archive

Chronological Thread  
  • From: Casey Harkins <charkins AT upl.cs.wisc.edu>
  • To: Eric Sandall <eric AT sandall.us>
  • Cc: SM Sorcery <sm-sorcery AT lists.ibiblio.org>
  • Subject: Re: [SM-Sorcery] splitting BUILD
  • Date: Thu, 11 Mar 2004 18:01:50 -0600 (CST)



On Thu, 11 Mar 2004, Eric Sandall wrote:

> Quoting Casey Harkins <charkins AT upl.cs.wisc.edu>:
> > Forgot to list these spells. This is the list from stable that references
> > SOURCE_DIRECTORY in POST_INSTALL:
> >
> > epsutil
> > gcc
> > gcc2
> > glibc
> > magicfilter2
> > openoffice
> > speedtouch
> > texinfo
> > xdirectfb
> > xfree86
> > xfree86-devel
> > xfree86-libs
> >
> >
> > Most of these only reference $SOURCE_DIRECTORY to remove it. The only two
> > exceptions are speedtouch and texinfo. speedtouch offers to view the
> > howto
> > from SOURCE_DIRECTORY, however it should be available in
> > /usr/share/doc/speedtouch (at least the POST_INSTALL says so if the user
> > opts not to view it then). texinfo uses the SOURCE_DIRECTORY to store
> > some
> > temporary files for generating a list of info files, this could easily be
> > done in /tmp.
>
> I believe that all files a spell needs to create temporarily should reside
> in
> $SOURCE_DIRECTORY only, otherwise people cannot cleanly remove a failed
> compile
> by just removing $SOURCE_DIRECTORY. Correct me if you think this idea is
> bad.
> ;)
>
> -sandalle
>

Nope, that does sound reasonable. I'd suggest moving these operations that
your SOURCE_DIRECTORY to POST_BUILD, but if changes are still tracked
there, we don't want to be tracking anything in SOURCE_DIRECTORY. Another
possibility would be yet another script, POST_CONFIGURE or something that
would do the other stuff that should be done upon resurrecting.

-casey





Archive powered by MHonArc 2.6.24.

Top of Page