On Mon, Sep 30, 2013 at 2:43 PM, Eric Shubert <[email protected]> wrote:

> The data files were omitted from the source tarball beginning with version
> 0.97.5. I thought that made sense. Now with 0.98 they appear to be back.
>
> Is there any easy/preferred way to "make install" (or "configure") without
> having the data files included? I'm packaging clamav-toaster, and am
> obtaining the data files in the %post processing, and I don't want them
> encumbering the rpm.
>
> I poked around the makefiles a bit, but I'm not very familiar with them.
> I'm thinking that a "make install-nodata" or some such would be nice.
>
> Thanks.
>
> --
> -Eric 'shubes'
>
> ______________________________**_________________
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/**clamav-faq<https://github.com/vrtadmin/clamav-faq>
> http://www.clamav.net/support/**ml <http://www.clamav.net/support/ml>
>

Eric,

I don't think we have a make target that will do that. To turn it off
manually is not a big change. Changing the Makefile targets to keep the
default behavior and add a new build target to do all the standard install
and skip this one step will be a bit trickier. You can open a feature
request bug on that and maybe we can add an easier way in the future, but
let me describe what else you could do in the interim.

The installation is using automake's "install-data-local" hook to do the
data file copying, and this is triggered from the Makefile in the
/clamav-devel/database directory. There are a couple different ways to skip
the step. The smallest change you can try is this:

After running configure, you will have a Makefile in the clamav-devel
folder. It will have a SUBDIRS line. Remove "database" from the list of
directories on the SUBDIRS line. After that, make commands in clamav-devel
will not enter the database folder.

NOTE: Next time you run configure, it will overwrite your change!

Give it a try and let me know if this does what you're looking for.

Dave R.

-- 
---
Dave Raynor
Sourcefire Vulnerability Research Team
[email protected]
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/support/ml

Reply via email to