packaging and config params
Kevin Broderick
gnucash at kevinbroderick.com
Thu Oct 5 15:17:07 EDT 2006
On 5 Oct 2006, at 1:38 PM, Derek Atkins wrote:
> Quoting Dave Reiser <dbreiser at earthlink.net>:
>> [CHOMP]
>> At this point, the overrides directory gets installed in
>> /sw/lib/gnucash/ instead of the being maintained in the usual
>> location of a make (provided I'm understanding what all "fink build
>> gnucash" is supposed to accomplish -- vs. "fink install gnucash")
>
> Um.. "make" should never touch /sw -- it shouldn't "install"
> anything.
> Only "make install" should. If "make" is actually touching the
> install tree it's a MAJOR bug, but I doubt that's what's going on.
> More likely you're not conveying to me the fink process and it's
> actually doing a "make install"..
Not exactly. See the fink build process description at <http://
fink.sourceforge.net/doc/packaging/reference.php?phpLang=en#build>
(Which, AFAIK, should be correct; however, I've never tried packaging
anything for fink, so AFAIK may not get you very far.)
>>> make install DESTDIR=/path/to/tempspace
>>
>> this might also be a problem, but at least I can ask a better
>> question over in the fink lists.
>
> Perhaps I don't understand fink. Doesn't fink build a .deb and then
> install the .deb?
That is correct. Fink supports both install from source and install
from binary; in the case of the former, it builds a DEB locally and
then installs it. However, there is an install process during the
build process that differs from the install step following the build
process (according to the aforementioned fink docs).
--Kevin
(who may or may not be correct in assuming that the fink docs are at
least close to correct)
More information about the gnucash-devel
mailing list