> I looks possible to set the OPKG_CONF_DIR environment variable to
> change the path where the opkg.conf file is located. I am using
> opkg_576-1_ar71xx.ipk and have tried it but can't get it to work:
>
> Would anybody have an idea ?
I dont think you can set the OPKG_CONF_DIR variable, but you should be
able to use:
opkg --offline_root=/tmp update
--
Camille Moncelier
http://devlife.org/
If Java had true garbage collection, most programs would
delete themselves upon execution.
On Tue, Feb 08, 2011 at 02:20:26PM +0100, Camille Moncelier wrote:
> > I looks possible to set the OPKG_CONF_DIR environment variable to
> > change the path where the opkg.conf file is located. I am using
> > opkg_576-1_ar71xx.ipk and have tried it but can't get it to work:
> >
> > Would anybody have an idea ?
>
> I dont think you can set the OPKG_CONF_DIR variable, but you should be
> able to use:
>
> opkg --offline_root=/tmp update
actually, setting OPKG_CONF_DIR does work for me.
For various reasons I need two separate opkg configurations in my rootfs,
I am using OPKG_CONF_DIR to point opkg to the alternative conf files and I
had to add a patch to separate the lib directories as well.
When accessing my "separate" opkg configuration I use a shell script as a
wrapper:
OPKG_CONF_DIR="/etc/opkg-add-ons" OPKG_LIB_DIR="/usr/lib/opkg-add-ons" opkg $@
The OPKG_LIB_DIR comes from my patch, but OPKG_CONF_DIR is stock and does
work for me (currently with revision 599, it was working with older revs as
well)
Kind regards,
Jin
> Maybe I don't get it but in http://code.google.com/p/opkg/source/browse/trunk/args.c?spec=svn524&r=8
> I can see getenv("OPKG_CONF_DIR").
> It's been removed in the latest versions ?
getenv("OPKG_CONF_DIR") is still here:
http://code.google.com/p/opkg/source/browse/trunk/libopkg/opkg_conf.c#451
You are looking at rev #8 which is prehistoric :) I just re-read your
mail and I think I foud your problem :)
export OPKG_CONF_DIR="/mnt/opt/etc/opkg.conf"
should be
export OPKG_CONF_DIR="/mnt/opt/etc"
It would help, yes. :-)