I am switching machines. I'm building a small Linux environment that is loaded onto a x86 device. It is compatible with the development environment. I copy /opt/perl to ~/devel/device_root and then use mksquashfs to create an image that is loaded into ram at boot.
Here is how I build perl today. I'm typing this from my head so it may not be exact.
PERL_INSTALL=/tmp/perl.`uuidgen` ./Configure -Dprefix=/opt/perl make -f Makefile install.perl DESTDIR=${PERL_INSTALL} # Now to install modules I need /opt/perl sudo ln -sf ${PERL_INSTALL}/opt/perl /opt/perl
I have at least 5 directories of perl modules
for i in `cat modules.list` do PERL_BIN=/opt/perl/bin/perl (cd $i && make -f OURMakefile install) || exit 1 done
Now I copy everything to the devel root
cp -dpvR ${PERL_INSTALL}/opt/perl ~/devel/root/opt
My idea is to use perlbrew so that I can use CPAN to download, build, and install modules instead of mean going into each directory. I also want to get rid of the sudo dependency. I thought If I use perlbrew to build perl and modules into ~/perlbrew/ I could simply copy the dist to ~/devel/root/. The problem is that the binary and files will be pointing to /home/cfowler/perlbrew/... and I do not want to create those symlinks on the device.
ChrisIn reply to Re^2: perlbrew copy to system
by Anonymous Monk
in thread perlbrew copy to system
by linxdev
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |