Michael Schmitt wrote: > Angus Leeming wrote: > >>>Angus> (I propose not to package python, perl or a shell environment. >>>Angus> Instead I think we should tell people to go and get their own.) >>> >>>How big are these things? >>> >>> >> >>ftp://ftp.python.org/pub/www.python.org/ftp/python/2.4.1/python-2.4.1.msi >>11.0MB >> >>http://downloads.activestate.com/ActivePerl/Windows/5.8/ActivePerl-5.8.6.811-MSWin32-x86-122208.msi >>12.6MB >> >>http://prdownloads.sf.net/mingw/MinGW-3.1.0-1.exe?download >>14.8MB >> >> > Angus, it think this list is not optimal: > > - You only need MSYS, not the full MinGW package
I see that now. > - MSYS already contains a version of perl Not good enough, I'm afraid. It expects UNIX style paths. In gerenal, it's going to be receiving DOS style paths. > - MSYS includes a version of "sed" that cannot process LyX' > "configure" script Ahhh. But it can if you fix the generated chconfig.sed so that it doesn't have DOS line endings. After I have run "make install", I run this script to produce something that I want to package. -- Angus
# (Note that this sed script contains TAB characters.)
# Append the dvi2 format after the dvi format.
/^ *\\\\Format[ ]\{1,\}dvi[ ]\{1,\}/a\
\\\\Format dvi2 dvi DirtyDVI ""
# Change the latex->dvi converter to latex->dvi2
# and append the dvi2->dvi converter
/^ *\\\\converter[ ]\{1,\}latex[ ]\{1,\}dvi[ ]\{1,\}/{
s/dvi/dvi2/
a\
\\\\converter dvi2 dvi "python \\\$\\\$s/scripts/clean_dvi.py \\\$\\\$i
\\\$\\\$o" ""
}
/^sed -f chkconfig.sed/i\
# Before running chkconfig.sed, remove the trailing "^M" characters\
# that can bugger up various versions of sed.\
sed 's/
$//' chkconfig.sed > chkconfig2.sed\
mv -f chkconfig2.sed chkconfig.sed
package_lyxwin.sh
Description: application/shellscript
