Previously Compiled Packages

I have a Slackware 10.0 system that I'll be replacing soon with an updated version. Now, this machine wasn't set up by me, and the person who set it up only has documentation of what was installed (Apache, PHP, and MySQL... all of which will also be upgraded), but not what configure options were passed when each was compiled from source.

Is there a way for these packages, or for packages in general, to determine what non-standard options were used based on the current install? Any help would be much appreciated, thank you.



Regards,
David
.

Relevant Pages

  • Re: Previously Compiled Packages
    ... Is there a way for these packages, or for packages in general, to ... Most non-standard options would have been passed at configure time. ... to believe there was something odd about the compile. ...
    (comp.os.linux.misc)
  • Re: Previously Compiled Packages
    ... Is there a way for these packages, or for packages in general, to ... Most non-standard options would have been passed at configure time. ... If you still have the original source you may see those options ...
    (comp.os.linux.misc)
  • Re: yum downgrading
    ... > What is the best way of replacing a package by an older version? ... > and I'd like to be able to install my present working version ... If you want to downgrade to a set of home-made packages, ...
    (Fedora)
  • FS: Complete Linux Recording Package Ready To Roll.
    ... How to install Rehmudi-2.0 ... if you don't have any sound, ... dependencies of Agnula Packages ... ... from the new kernel. ...
    (comp.os.linux.misc)
  • Re: Complete Linux Recording Package Ready To Roll.
    ... How to install Rehmudi-2.0 ... if you don't have any sound, ... dependencies of Agnula Packages ... ... from the new kernel. ...
    (comp.os.linux.misc)