| View previous topic :: View next topic |
| Author |
Message |
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
 Posted: Wed Mar 18, 2009 10:45 am Post subject: |
 |
|
copy the script somewhere, then modify the PROFILE variable, so that it's equal to "hzotbwlp.default"
close firefox, run the script, look at the output of the 'mount' command, then read this thread again, till you get something
_________________
The End of the Internet! |
|
| Back to top |
|
 |
shgadwa
Guru
Joined: 12 Mar 2009
Posts: 327
|
| Posted: Wed Mar 18, 2009 12:21 pm Post subject: |
|
|
| Quote: | localhost ~ # #!/bin/bash
localhost ~ #
localhost ~ # # Change this to match your correct profile
localhost ~ # PROFILE="profiles.ini"
localhost ~ #
localhost ~ # cd "${HOME}/.mozilla/firefox"
localhost firefox #
localhost firefox # if test -z "$(mount | grep -F "${HOME}/.mozilla/firefox/${PROFILE}" )"
> then
> mount "${HOME}/.mozilla/firefox/${PROFILE}"
> fi
[mntent]: line 20 in /etc/fstab is bad
mount: mount point /root/.mozilla/firefox/profiles.ini is not a directory
localhost firefox #
localhost firefox # if test -f "${PROFILE}/.unpacked"
> then
> tar --exclude '.unpacked' -cpf packed.tmp.tar "$PROFILE"
> mv packed.tar packed.tar.old
> mv packed.tmp.tar packed.tar
> else
> tar xpf packed.tar &&\
> touch "${PROFILE}/.unpacked"
> fi
bash: : command not found
touch: cannot touch `profiles.ini/.unpacked': Not a directory |
|
|
| Back to top |
|
|
shgadwa
Guru
Joined: 12 Mar 2009
Posts: 327
|
| Posted: Wed Mar 18, 2009 12:22 pm Post subject: |
|
|
And I do not even have a profile directory... I do have a file called profiles.ini in the /firefox folder.
EDIT: Sorry about the double post... I will have to read it a few times then when I get time. Later.
Thanks.
~Shawn
Last edited by shgadwa on Wed Mar 18, 2009 1:01 pm; edited 1 time in total |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Wed Mar 18, 2009 12:39 pm Post subject: |
|
|
No need to double-post.
here is a hint:
| truc wrote: | | then read this thread again, till you get something |
_________________
The End of the Internet! |
|
| Back to top |
|
|
shgadwa
Guru
Joined: 12 Mar 2009
Posts: 327
|
| Posted: Wed Mar 18, 2009 2:40 pm Post subject: |
|
|
| OK............... I read this thread a few times. I think it works, but then again, I think it does not work. That is to say, I do not get any errors but it never creates or mounts a directory anywhere that I can see and my .mozilla/firefox/ profile directory just keeps filling up with more cache and stuff. I take its not working. To be honest I'm tired of reading the same thing over and over again. Oh well, thats alright... its not like its super slow anyway. |
|
| Back to top |
|
|
Enlight
Advocate
Joined: 28 Oct 2004
Posts: 3519
Location: Alsace (France)
|
| Posted: Thu Mar 19, 2009 7:12 pm Post subject: |
|
|
| belikeyeshua wrote: | | Quote: | localhost ~ # #!/bin/bash
localhost ~ # # Change this to match your correct profile
localhost ~ # PROFILE="profiles.ini"
|
|
This is where you're wrong! profile is [something].default in ~/.mozilla/firefox/ |
|
| Back to top |
|
|
Sadako
Advocate
Joined: 05 Aug 2004
Posts: 3792
Location: sleeping in the bathtub
|
| Posted: Thu Mar 19, 2009 8:47 pm Post subject: |
|
|
| Enlight wrote: | | belikeyeshua wrote: | | Quote: | localhost ~ # #!/bin/bash
localhost ~ # # Change this to match your correct profile
localhost ~ # PROFILE="profiles.ini"
|
|
This is where you're wrong! profile is [something].default in ~/.mozilla/firefox/ |
Howsabouts this? | Code: | PROFDIR="${HOME}/.mozilla/firefox/"
PROFILE="${PROFDIR}/$(grep Path= "${PROFDIR}/profiles.ini" | cut -d = -f 2)" |
Assuming you only have one profile defined within profiles.ini...
_________________
"You have to invite me in" |
|
| Back to top |
|
|
shgadwa
Guru
Joined: 12 Mar 2009
Posts: 327
|
| Posted: Fri Mar 20, 2009 11:03 am Post subject: |
|
|
Yes, I figured that out.... after reading the thread a few times. 
I have used the right file (blahblah.default)... but it still does not work. |
|
| Back to top |
|
|
Sadako
Advocate
Joined: 05 Aug 2004
Posts: 3792
Location: sleeping in the bathtub
|
| Posted: Fri Mar 20, 2009 12:35 pm Post subject: |
|
|
| Hopeless wrote: | | Enlight wrote: | | belikeyeshua wrote: | | Quote: | localhost ~ # #!/bin/bash
localhost ~ # # Change this to match your correct profile
localhost ~ # PROFILE="profiles.ini"
|
|
This is where you're wrong! profile is [something].default in ~/.mozilla/firefox/ |
Howsabouts this? | Code: | PROFDIR="${HOME}/.mozilla/firefox/"
PROFILE="${PROFDIR}/$(grep Path= "${PROFDIR}/profiles.ini" | cut -d = -f 2)" |
Assuming you only have one profile defined within profiles.ini... |
Actually, the above is completely unnecessary, and rather silly really.
All you really need is this; | Code: | | PROFILE="${HOME}/.mozilla/firefox/*.default/" |
_________________
"You have to invite me in" |
|
| Back to top |
|
|
Gentooser
n00b
Joined: 11 Mar 2009
Posts: 16
|
| Posted: Sun Mar 29, 2009 12:41 pm Post subject: |
|
|
Cannot edit crontab 
| Code: |
/bin/sh: /usr/bin/vi: No such file or directory
crontab: "/usr/bin/vi" exited with status 127 |
|
|
| Back to top |
|
|
Dont Panic
Guru
Joined: 20 Jun 2007
Posts: 322
Location: SouthEast U.S.A.
|
| Posted: Fri Apr 03, 2009 7:03 pm Post subject: |
|
|
It looks like something has gone amiss with your default editor setting.
Normally, in Gentoo, this is set for /usr/bin/nano.
One possibility is that your default editor was changed to vim, but the package app-editors/vim was either not installed or un-installed.
You also may want to edit your /etc/rc.conf file, and change your default editor to one that is installed (/usr/bin/nano is usually the default). |
|
| Back to top |
|
|
loudmax
n00b
Joined: 30 Mar 2005
Posts: 7
|
| Posted: Fri Apr 10, 2009 10:43 pm Post subject: Advanced version of the pack firefox script |
|
|
I rewrote stevenrobertson's script to include compression and some error checking. Compression isn't strictly necessary, but it's desirable for machines with SSD media such as netbooks.
| Code: |
#!/bin/bash
################################################################################################
## Firefox tmpfs utility
# see http://forums.gentoo.org/viewtopic-t-717117.html
#
# 1. check environment:
# a. entry in /etc/fstab
# b. profile dir is empty if not mounted tmpfs
# if either condition is false, print setup info
# 2. check pack direction:
# tmpfs is mounted
# pack it to archive
# tmpfs not mounted
# mount and unpack
#
################################################################################################
## Change this to match your correct profile
# If blank, this script will grab whatever profile is most recent
#
PROFILE=""
FFOX_HOME="${HOME}/.mozilla/firefox"
## Preferred compression utility
# We're going for speed, the options are: none, gzip or lzop
# If blank, the script will select lzop if available or default to gzip
#
COMPRESSOR=""
export GZIP='--fast' # option for gzip
## get more recent profile in home dir if not defined
#
if [[ ${PROFILE} == "" ]]; then
PROFILE=$( basename $( ls -rdt ${HOME}/.mozilla/firefox/*.default | tail -n 1 ) )
fi
## Check that environment is set up right
# a. We found the ffox profile
# b. There should be an entry in /etc/fstab
# c. The profile should be an empty directory if the tmps is unmounted
#
FAILED_CHECKS=0
if [[ ${PROFILE} == "" ]]; then
echo "Cannot find firefox profile directory"
exit 3
fi
if [[ $( grep "${FFOX_HOME}/${PROFILE}" /etc/fstab ) == "" ]]; then
FAILED_CHECKS=1
fi
if test -z "$(mount | grep -F "${FFOX_HOME}/${PROFILE}" )"; then
if [[ -d "${FFOX_HOME}/${PROFILE}" ]]; then
FAILED_CHECKS=$( ls ${FFOX_HOME}/${PROFILE}/* 2> /dev/null| wc -l )
fi
fi
if [[ ${FAILED_CHECKS} != 0 ]]; then
echo "See the Gentoo forums for an explanation of how this works: http://forums.gentoo.org/viewtopic-t-717117.html"
echo ""
echo "Make sure a line like this one is in /etc/fstab:"
GID=$( awk -v FS=: '/'"${USER}"'/{print $4 ; quit}' /etc/passwd )
echo "firefox ${FFOX_HOME}/${PROFILE} tmpfs noauto,user,exec,uid=${UID},gid=${GID} 0 0"
echo ""
echo "Exit firefox and tar a copy of the profile:"
echo " cd ${FFOX_HOME}"
echo " tar -czpf ${PROFILE}.tar.gz ${PROFILE} #(this is for gzip compression)"
echo " OR"
echo " tar -cp ${PROFILE} | lzop -c > ${PROFILE}.tar.lzo #(this is for lzop compression)"
echo " OR"
echo " tar -cpf ${PROFILE}.tar ${PROFILE} #(this is for no compression)"
echo "Back up your profile and create an empty directory:"
echo " mv -i ${PROFILE} ${PROFILE}.bak && mkdir ${PROFILE}"
exit 2
fi
## define how to pack archive
#
PACKLZO="tar --exclude '.unpackt' -C ${FFOX_HOME} -cp \"${PROFILE}\" | lzop -c > ${FFOX_HOME}/${PROFILE}.tar.lzo"
UNPACKLZO="lzop -cd \"${FFOX_HOME}/${PROFILE}.tar.lzo\" | tar -C ${FFOX_HOME} -xp"
PACKGZP="tar --exclude '.unpackt' -C ${FFOX_HOME} -czpf ${FFOX_HOME}/${PROFILE}.tar.gz \"${PROFILE}\""
UNPACKGZP="tar -C ${FFOX_HOME} -xzpf ${FFOX_HOME}/${PROFILE}.tar.gz"
PACKTAR="tar --exclude '.unpackt' -C ${FFOX_HOME} -cpf ${FFOX_HOME}/${PROFILE}.tar \"${PROFILE}\""
UNPACKTAR="tar -C ${FFOX_HOME} -xpf ${FFOX_HOME}/${PROFILE}.tar"
## set pack/unpack command based on available utilities
#
PACKCMD=""
UNPACKCMD=""
if [[ ${COMPRESSOR} == "" ]]; then
if [[ $( which lzop ) != "" ]] && [[ -f ${FFOX_HOME}/${PROFILE}.tar.lzo ]] ; then
PACKCMD=${PACKLZO}
UNPACKCMD=${UNPACKLZO}
else
PACKCMD=${PACKGZP}
UNPACKCMD=${UNPACKGZP}
fi
elif [[ ${COMPRESSOR} == "lzop" ]]; then
if test -z "which lzop"; then
echo "Could not find lzop"
exit 4
fi
elif [[ ${COMPRESSOR} == "gzip" ]]; then
PACKCMD=${PACKGZP}
UNPACKCMD=${UNPACKGZP}
elif [[ ${COMPRESSOR} == "none" ]]; then
PACKCMD=${PACKTAR}
UNPACKCMD=${UNPACKTAR}
fi
## Check mount point
#
if test -z "$(mount | grep -F "${FFOX_HOME}/${PROFILE}" )"; then
mount "${FFOX_HOME}/${PROFILE}"
if [[ $? != 0 ]]; then
echo "Failed to mount tmpfs"
exit 1
fi
fi
## Things look good, so pack if running profile found, or unpack if profile empty
#
if [[ -f "${FFOX_HOME}/${PROFILE}/.unpackt" ]]; then
echo -n "tarring firefox... "
START_TIME=$( date +%s )
bash -c "${PACKCMD}"
if [[ $? != 0 ]]; then
echo "Failed to pack the profile"
exit 4
fi
END_TIME=$( date +%s )
PACK_TIME=$(( ${END_TIME} - ${START_TIME} ))
echo "done in ${PACK_TIME} seconds!"
else
bash -c "${UNPACKCMD}"
echo "unpacking!"
if [[ $? != 0 ]]; then
echo "Failed to unpack the profile"
exit 5
fi
touch "${FFOX_HOME}/${PROFILE}/.unpackt"
fi
|
Last edited by loudmax on Mon Apr 13, 2009 2:58 pm; edited 1 time in total |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Sat Apr 11, 2009 6:37 pm Post subject: |
|
|
I haven't read the whole script, but, I don't see why you launch a new bash process to execute eg "${UNPACKCMD}"
| Code: | | bash -c "${UNPACKCMD}" |
Also, (as a side note  ):
You can replace this:
| Code: | | grep -m 1 ${USER} /etc/passwd | awk 'BEGIN{FS=":"}{print $4}' |
with:
| Code: | | awk -v FS=: '/'"${USER}"'/{print $4 ; quit}' /etc/passwd |
EDIT: now that I think about what you really want, I think you can even replace the whole command with
_________________
The End of the Internet!
Last edited by truc on Mon Apr 13, 2009 4:42 pm; edited 1 time in total |
|
| Back to top |
|
|
loudmax
n00b
Joined: 30 Mar 2005
Posts: 7
|
| Posted: Mon Apr 13, 2009 2:46 pm Post subject: |
|
|
| truc wrote: | | I haven't read the whole script, but, I don't see why you launch a new bash process to execute eg "${UNPACKCMD}" |
To tell the truth, I'm not sure why either. If I try to execute it directly without wrapping bash around it, I get this error:
| Code: | $ packfox.sh
lzop: cannot use both `-c' and `-p'
Usage: lzop [-dxlthIVL19] [-qvcfFnNPkUp] [-o file] [-S suffix] [file..]
unpacking! |
or this error:
| Code: | $ packfox.sh
packfox.sh: line 137: lzop -cd "/home/user/.mozilla/firefox/abcd1234.default.tar.lzo" | tar -C /home/user/.mozilla/firefox -xp: No such file or directory |
I get errors regardless of whether I'm using lzop, gzip, or no compression. If I wrap the command inside a spawned bash process, it comes out fine.
| truc wrote: | You can replace this:
| Code: | | grep -m 1 ${USER} /etc/passwd | awk 'BEGIN{FS=":"}{print $4}' |
with:
| Code: | | awk -v FS=: '/'"${USER}"'/{print $4 ; quit}' /etc/passwd |
|
Oh yes, that is nice. I'll update the script. |
|
| Back to top |
|
|
boerKrelis
Apprentice
Joined: 01 Jul 2003
Posts: 241
Location: The Netherlands
|
| Posted: Thu May 07, 2009 4:27 pm Post subject: |
|
|
Here's a rewrite which uses inotify, so it only tars whenever anything changes.
Read the comments in the file to find out how to handle this.
| Code: |
#!/bin/bash
# Save this script as 'packfox' and hard/symlink it as 'packfox-daemon'
# (or the other way around) in the same dir.
# 'packfox' will invoke the packing.
# 'packfox-daemon' will run a loop, watching for changes, calling 'packfox' if any.
# both incantations will do checks, mounting, and unpacking.
# Change this to match your correct profile
PROFILE="bling"
PFDIR="${HOME}/.mozilla/firefox"
# Tar every .. seconds (regardless of changes)
TMOUT="900"
# But not more often than every .. seconds (regardless of changes)
TMMIN="60"
# Regex for which files not to act on when they're changed.
# Use inotifywait -m -e modify -e move -e create -e delete --exclude '(/Cache/)' -r your_profile_dir
# and do some browsing to determine which regex will be right for YOU.
IEXCL="(.sqlite-journal$)|(\-log.txt$)|(cookies.sqlite$)|(sessionstore\-[0-9].js$)|(/weave/)|(/Cache/)"
# Have you read everything and have you made the necessary adjustments? Then remove the line below ;-)
echo "I should read the comments and adjust the variables before running this script" && exit 2
# No user servicable parts below this line.
TGT="${PFDIR}/${PROFILE}"
function seppuku(){
echo "${1}"
exit 2
}
test -d "${PFDIR}" || seppuku "Profile dir doesn't exist"
if [ -z "$(mount -t tmpfs | grep -F "${TGT}" )" ]
then
mount "${PFDIR}/${PROFILE}" || seppuku "Mounting of profile's tmpfs failed; check fstab"
fi
test -f "${TGT}/.unpacked" || tar -xpf "${PFDIR}/packed.tar" -C "${PFDIR}" && touch "${TGT}/.unpacked"
if [ "$(basename ${0})" == "packfox-daemon" ]
then
which inotifywait >/dev/null 2>&1 || seppuku "Install sys-fs/inotify-tools first".
while true
do inotifywait -q -q -t ${TMOUT} -e modify -e move -e create -e delete --exclude "${IEXCL}" \
-r "${PFDIR}/${PROFILE}"; "$(dirname "${0}")/packfox"; sleep ${TMMIN}
done
exit
fi
cd "${PFDIR}"
tar --exclude '.unpacked' -cpf "${PFDIR}/packed.tmp.tar" "${PROFILE}"
mv "${PFDIR}/packed.tar" "${PFDIR}/packed.tar.old"
mv "${PFDIR}/packed.tmp.tar" "${PFDIR}/packed.tar"
|
|
|
| Back to top |
|
|
iamboredr
n00b
Joined: 09 May 2009
Posts: 10
|
| Posted: Sat May 09, 2009 7:07 pm Post subject: |
|
|
| it would affect the browsers speed? |
|
| Back to top |
|
|
gigio
n00b
Joined: 17 May 2009
Posts: 1
|
| Posted: Sun May 17, 2009 12:43 pm Post subject: |
|
|
Hi,
I'm very interested in this,
Could anyone please post the shell commands to run the script in Mac OS X 10.4 ?
I tried to follow all of your instructions, but i get this error when mounting tmpfs: "unknown special file or file system."
It probably has to do with fstab,
Anyone can help?
Thank you very much in advance  |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Sun May 17, 2009 3:19 pm Post subject: |
|
|
| gigio wrote: | Hi,
I'm very interested in this,
Could anyone please post the shell commands to run the script in Mac OS X 10.4 ?
I tried to follow all of your instructions, but i get this error when mounting tmpfs: "unknown special file or file system."
It probably has to do with fstab,
Anyone can help?
Thank you very much in advance |
googling for tmpfs osx ~brings this link: Blazing Fast Firefox using OSX RamDisk
_________________
The End of the Internet! |
|
| Back to top |
|
|
Ch00k
n00b
Joined: 02 May 2009
Posts: 55
|
| Posted: Sat May 30, 2009 10:14 pm Post subject: |
|
|
| Well, I wonder why would you need a cron entry for the script. Wouldn't it be enough to execute the script for just two times: on login (boot) and on logout (shutdown). What files do I have to add this script to? Are they .bash_profile and .bash_logout? |
|
| Back to top |
|
|
Ch00k
n00b
Joined: 02 May 2009
Posts: 55
|
| Posted: Sat May 30, 2009 10:29 pm Post subject: |
|
|
| Hopeless wrote: | | One thing to bear in mind is that variables in these files override what you may find in make.conf, rather than add to them, so if you have just 'CFLAGS="-O3"' in the above example ffmpeg will be compiled without any -march set. |
I also have a question regarding this post. Does the above mean that if you do not set CHOST, MAKEOPTS, GENTOO_MIRRORS etc, then they will leave unset for this specific package? Well, without GENTOO_MIRRORS you will not be able to even fetch it |
|
| Back to top |
|
|
boerKrelis
Apprentice
Joined: 01 Jul 2003
Posts: 241
Location: The Netherlands
|
| Posted: Sun May 31, 2009 11:44 am Post subject: |
|
|
Ch00k, you're right wrt needing to run the script >2 times. It depends on how much of your browsing history, open tabs, bookmarks, entered passwords, stored cookies you are willing to lose if the unforeseen happens (eg you crash your machine).
If you want to avoid doing unnecessary work (tarring even though nothing's changed) and want to control upper and lower bounds to how often the tarring should take place I'd recommend my inotify script posted in this thread.
Your ~/.bash_login only gets sourced when you execute bash as a login shell. From this it follows that that is not a good place to call the script from, unless you don't boot into X and bash is your login shell.
I run my 'packfox-daemon' from an XDG entry in ~/.config/autostart .
| Quote: |
I also have a question regarding this post. Does the above mean that if you do not set CHOST, MAKEOPTS, GENTOO_MIRRORS etc, then they will leave unset for this specific package? Well, without GENTOO_MIRRORS you will not be able to even fetch it
|
If you don't override stuff on the commandline they will be taken from make.conf . If not found there, portage will leave them unset or, in some cases, make up something by itself.
This can be illustrated by doing something like
| Code: | CFLAGS="-foobar" emerge --info
|
and observing the difference between this and a regular
You can override any variable. This is a generic mechanism. Observe the output from
That's all the variables assigned in your current environment (such as your current bash shell).
You can figure out how it works by observing the difference in output between
and
| Code: | | PATH="/tmp" /usr/bin/which ls |
You can make variables persistent in the current environment by using export. For instance, try
and observe that it has now become quite difficult to do stuff in this particular shell ;-) |
|
| Back to top |
|
|
Ch00k
n00b
Joined: 02 May 2009
Posts: 55
|
| Posted: Sun May 31, 2009 3:23 pm Post subject: |
|
|
boerKrelis, many thanks for your reply. Though, I actually mean the following:
| Quote: | Sure, tbh I can't even remember how/where I learned about it, but I know full well about the lack of documentation for this feature.
Take (for example) media-video/ffmpeg, if you have CFLAGS="-O2 -march=k8" in make.conf, but wish to have ffmpeg compiled with -O3, you'd create the file (and parent directories) '/etc/portage/env/media-video/ffmpeg', and simply add 'CFLAGS="-O3 -march=k8"' to it, basically the same format as make.conf, which is really just for setting shell variables.
That's basically all there is to it, and it has lots of uses, you can override many variables which you might set in make.conf, CFLAGS just being the most obvious one, but another fantastic one is EXTRA_ECONF, to which you can add extra --enable-foo or --disable-foo arguments to ./configure (presuming the ebuild uses econf).
One thing to bear in mind is that variables in these files override what you may find in make.conf, rather than add to them, so if you have just 'CFLAGS="-O3"' in the above example ffmpeg will be compiled without any -march set.
Another thing is not everything seems to work, one example of something which doesn't is ALSA_PCM_PLUGINS for media-libs/alsa-lib, and probably the same holds true for VIDEO_CARDS, LINGUAS and the like (run `emerge -v --info | grep USE_EXPAND` for a list), but most likely the reason for this is they are in fact just USE flags, and their real format is alsa_pcm_plugins_FOO, so adding alsa_pcm_plugins_rate and similar to /etc/portage/package.use should do the trick there. |
So... if you create this /etc/portage/env/media-video/ffmpeg file and post there, say, CFLAGS="-O2 -march=k8", then will all the other variables, like CHOST, MAKEOPTS, GENTOO_MIRRORS be taken from /etc/make.conf, or will they be left unset. From the "One thing to bear in mind is that variables in these files override what you may find in make.conf, rather than add to them, so if you have just 'CFLAGS="-O3"' in the above example ffmpeg will be compiled without any -march set." I concluded that they will be left unset. Or maybe the files in /etc/portage/env are intended to be used for posting into them the CFLAGS variable only, and all the rest is taken from /etc/make.conf?
Sorry to post this in an unrelated thread, but I'm really concerned in learning this feature |
|
| Back to top |
|
|
loki99
Advocate
Joined: 10 Oct 2003
Posts: 2056
Location: Vienna, €urope
|
| Posted: Sun May 31, 2009 6:25 pm Post subject: |
|
|
| Thx for the tip! It reduced the initial startup time by 50% for me and the whole thing just feel a tad faster. |
|
| Back to top |
|
|
Sadako
Advocate
Joined: 05 Aug 2004
Posts: 3792
Location: sleeping in the bathtub
|
| Posted: Wed Jun 10, 2009 10:44 pm Post subject: |
|
|
| Ch00k wrote: | boerKrelis, many thanks for your reply. Though, I actually mean the following:
| Quote: | Sure, tbh I can't even remember how/where I learned about it, but I know full well about the lack of documentation for this feature.
Take (for example) media-video/ffmpeg, if you have CFLAGS="-O2 -march=k8" in make.conf, but wish to have ffmpeg compiled with -O3, you'd create the file (and parent directories) '/etc/portage/env/media-video/ffmpeg', and simply add 'CFLAGS="-O3 -march=k8"' to it, basically the same format as make.conf, which is really just for setting shell variables.
That's basically all there is to it, and it has lots of uses, you can override many variables which you might set in make.conf, CFLAGS just being the most obvious one, but another fantastic one is EXTRA_ECONF, to which you can add extra --enable-foo or --disable-foo arguments to ./configure (presuming the ebuild uses econf).
One thing to bear in mind is that variables in these files override what you may find in make.conf, rather than add to them, so if you have just 'CFLAGS="-O3"' in the above example ffmpeg will be compiled without any -march set.
Another thing is not everything seems to work, one example of something which doesn't is ALSA_PCM_PLUGINS for media-libs/alsa-lib, and probably the same holds true for VIDEO_CARDS, LINGUAS and the like (run `emerge -v --info | grep USE_EXPAND` for a list), but most likely the reason for this is they are in fact just USE flags, and their real format is alsa_pcm_plugins_FOO, so adding alsa_pcm_plugins_rate and similar to /etc/portage/package.use should do the trick there. |
So... if you create this /etc/portage/env/media-video/ffmpeg file and post there, say, CFLAGS="-O2 -march=k8", then will all the other variables, like CHOST, MAKEOPTS, GENTOO_MIRRORS be taken from /etc/make.conf, or will they be left unset. From the "One thing to bear in mind is that variables in these files override what you may find in make.conf, rather than add to them, so if you have just 'CFLAGS="-O3"' in the above example ffmpeg will be compiled without any -march set." I concluded that they will be left unset. Or maybe the files in /etc/portage/env are intended to be used for posting into them the CFLAGS variable only, and all the rest is taken from /etc/make.conf?
Sorry to post this in an unrelated thread, but I'm really concerned in learning this feature |
Sorry I didn't reply sooner, updates to this thread weren't bumping it in my "egosearch".
Anyways, variables like CHOST & co will only be overridden if you set them in the /etc/portage/env/cat/package file, ie if you don't set them they'll use what's set in make.conf.
The point I was trying to make was that you can't just add new flags to a variable like CFLAGS, ie if you have CFLAGS="-march=i686 -O2" in make.conf and you want to add -fomit-frame-pointer for one particular package via /etc/portage/env, you need to add CFLAGS="-march=i686 -O2 -fomit-frame-pointer" rather than just CFLAGS="-fomit-frame-pointer", as with the latter there'll be no -march or optimization switch passed to gcc during compile.
However, only the flags you explicitly set in the env file will override those in make.conf, meaning if you don't set CHOST or whatever in that file it'll still use the CHOST setting in make.conf, regardless of whatever else you have set in the env file.
A hope this clears it up a little, sorry it was kinda vague before.
_________________
"You have to invite me in" |
|
| Back to top |
|
|
El_Goretto
Moderator
Joined: 29 May 2004
Posts: 3169
Location: Paris
|
| Posted: Thu Jun 25, 2009 9:53 am Post subject: |
|
|
Hi everyone,
I wanna use this script, but I dont understand why using so dirty "hacks" (local.stop or crontab... argh) to ensure that the script is run after ff is closed...
Why not simply use a simple "wrapper", such as this totally complex:
| Code: | #!/bin/bash
/usr/local/bin/pack_ffox.sh
/usr/bin/firefox $*
/usr/local/bin/pack_ffox.sh
|
With a generic pack_ffox.sh using Hopeless modification:
| Code: | #!/bin/bash
PROFDIR="${HOME}/.mozilla/firefox"
PROFILE="$(grep Path= "${PROFDIR}/profiles.ini" | cut -d = -f 2)"
cd "${HOME}/.mozilla/firefox"
if test -z "$(mount | grep -F "${HOME}/.mozilla/firefox/${PROFILE}" )"
then
mount "${HOME}/.mozilla/firefox/${PROFILE}"
fi
if test -f "${PROFILE}/.unpacked"
then
tar --exclude '.unpacked' -cpf packed.tmp.tar "$PROFILE"
mv packed.tar packed.tar.old
mv packed.tmp.tar packed.tar
else
tar xpf packed.tar &&\
touch "${PROFILE}/.unpacked"
fi
|
Or did I miss something?
_________________
-TrueNAS & jails: µ-serv Gen8 E3-1260L, 16Go ECC + µ-serv N40L, 10Go ECC
-Réseau: APU2C4 (OpenWRT) + GS726Tv3 + 2x GS108Tv2 + Archer C5v1 (OpenWRT)
Last edited by El_Goretto on Fri Jun 26, 2009 7:59 pm; edited 1 time in total |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Documentation, Tips & Tricks
