chrome://messenger/locale/messengercompose/composeMsgs.properties:
On Thu, 11 Feb 2010 15:39:48 -0800, Mark Knecht wrote:
Volker is. I am not sure I am and I'm not sure that Neil was talking
about quickpkg which is what I am using so far. The command
quickpkg --include-configs
says it includes the configs. That's what I thought we (you and I
Alan) were talking about.
On the other hand I presumed (apparently incorrectly) that the
FEATURES="buildpkg" (which is what I think Neil is speaking about)
gave me the same option but I now guess it doesn't.
I was talking about the difference between quickpkg and buildpkg in
response to your statement "One thing I haven't found so far is what to
put in make.conf to get the buildpkg feature to include the configs."
I'm not sure that is doable actually. If you use buildpkg, there is no
config except the "virgin" one that comes from the tarball. From my
understanding, emerge builds the package, saves a copy to
/usr/portage/All then installs the package to where ever it goes,
presumably /.
I think I see what you mean but I don't think there is anything to be
saved since it is not installed when it is done. Someone correct me if
I am wrong here.
Dale
:-) :-)
