On Thu, Oct 03, 2002 at 06:49:38PM +0200, Lars Gullik Bj?nnes wrote:
> [EMAIL PROTECTED] writes:
> 
> | 1) 
> >
> | Instead of 
> >
> | %{_datadir}/texmf/tex/latex/%{name}
> >
> | in the files section, should not lyx be installed under
> >
> | %{_datadir}/texmf.local/tex/latex/%{name}
> >
> | More generally, should not the rpm get the TEXMFLOCAL variable from
> | the tex environment with something like
> >
> | kpsewhich --expand-var='$TEXMFLOCAL'
> >
> | and similarly (in case needed)
> >
> | kpsewhich --expand-var='$TEXMFMAIN'
> 
> Possibly, this is for the latex class files/styles that is in the lyx
> distribution, right?

Yes.
> | Is reLyX still needed?  It seems there is a builtin tex import in LyX
> | (which works pretty well).
> 
> yes, that is reLyX running...(behind the scenes)
> 

Then I do not understand why the line

# Fix reLyX perl program if the prefix is non-standard
if [ "%{_prefix}" != "/usr" ]
then
    perl -pi -e "s!/usr/share/lyx!%{_datadir}/lyx!" \
    
            %{_bindir}/reLyX
            fi

Does not the standard installation take care of this?
            

> | 4) 
> >
> | Why is the line
> >
> | gzip -f9 ${RPM_BUILD_ROOT}%{_mandir}/man?/*
> >
> | Does not RH automatically gzips the man pages?
> 
> not on install?

Do not understand.  Rpm packages the man pages gzipped automatically.

> 
> | 5) 
> >
> | More generally: would not there be a possibility to use the
> | %_configure, %_make, etc macros?
> 
> Sure... can you dump be the info on those macros?

>From /usr/lib/rpm/macros:

# This is an improved version of %configure (from PLD team).
%configure \
  CFLAGS="${CFLAGS:-%optflags}" ; export CFLAGS ; \
  CXXFLAGS="${CXXFLAGS:-%optflags}" ; export CXXFLAGS ; \
  FFLAGS="${FFLAGS:-%optflags}" ; export FFLAGS ; \
  ./configure --host=%{_host} --build=%{_build} \\\
        --target=%{_target_platform} \\\
        --program-prefix=%{?_program_prefix} \\\
        --prefix=%{_prefix} \\\
        --exec-prefix=%{_exec_prefix} \\\
        --bindir=%{_bindir} \\\
        --sbindir=%{_sbindir} \\\
        --sysconfdir=%{_sysconfdir} \\\
        --datadir=%{_datadir} \\\
        --includedir=%{_includedir} \\\
        --libdir=%{_libdir} \\\
        --libexecdir=%{_libexecdir} \\\
        --localstatedir=%{_localstatedir} \\\
        --sharedstatedir=%{_sharedstatedir} \\\
        --mandir=%{_mandir} \\\
        --infodir=%{_infodir}

#------------------------------------------------------------------------------
# The make install analogue of %configure:
%makeinstall \
  make \\\
        prefix=%{?buildroot:%{buildroot}}%{_prefix} \\\
        exec_prefix=%{?buildroot:%{buildroot}}%{_exec_prefix} \\\
        bindir=%{?buildroot:%{buildroot}}%{_bindir} \\\
        sbindir=%{?buildroot:%{buildroot}}%{_sbindir} \\\
        sysconfdir=%{?buildroot:%{buildroot}}%{_sysconfdir} \\\
        datadir=%{?buildroot:%{buildroot}}%{_datadir} \\\
        includedir=%{?buildroot:%{buildroot}}%{_includedir} \\\
        libdir=%{?buildroot:%{buildroot}}%{_libdir} \\\
        libexecdir=%{?buildroot:%{buildroot}}%{_libexecdir} \\\
        localstatedir=%{?buildroot:%{buildroot}}%{_localstatedir} \\\
        sharedstatedir=%{?buildroot:%{buildroot}}%{_sharedstatedir} \\\
        mandir=%{?buildroot:%{buildroot}}%{_mandir} \\\
        infodir=%{?buildroot:%{buildroot}}%{_infodir} \\\
  install

Please note

# The configure macro should be invoked as %configure (rather than %{configure})
# because the rest of the arguments will be expanded using %*.

Mate

Reply via email to