I see the same thing here... However, I'm not sure if this is intended or not, but the RPM that gets built from a make rpm-package only has the bare bones binaries, config files and docs and no plugins. I suspect that's because the spec file was never updated. Before I go messing with the spec file, is this the problem? Also, I'm not sure what PLUGINS_DIR would get set to when building the RPM, so I don't know where to put the plugins in the SPEC file.

Thanks,
Anand


At 01:32 PM 8/14/2002 -0700, Guy Harris wrote:
On Wed, Aug 14, 2002 at 02:57:22PM -0400, Khachaturov Vassilii wrote:
> Am I the only one who has to
>       cd epan && ln -s ../INSTALL ../COPYING .
> in order to enable 'make dist', 'make rpm-package' etc. to work?

"make dist" worked for me from a CVS tree.

If I go to the "epan" directory, and look at INSTALL and COPYING, I see:

        hostname$ file INSTALL COPYING
        INSTALL: symbolic link to /usr/local/share/automake/INSTALL
        COPYING: symbolic link to /usr/local/share/automake/COPYING

so presumably somehow automake made those links at some point.
_______________________________________________
Ethereal-dev mailing list
[EMAIL PROTECTED]
http://www.ethereal.com/mailman/listinfo/ethereal-dev

-- Anand V. Narwani, CCIE 3892 Advanced Engineering Services Cisco Systems, Inc. Direct/Fax: 919.392.3404 Email: [EMAIL PROTECTED]

"Meddle not in the affairs of dragons, for you are crunchy and taste good with ketchup"




Reply via email to