With which telenet command can I decide am I use OE1.6 or OE2.0

    Zitat von Klix

    opkg list-installed|grep 'enigma2 '


    OE2.0:

    Code
    root@vusolo:/usr/bin# opkg list-installed|grep 'enigma2 '
enigma2 - experimental-git20121128-r17-bh12
task-vuplus-enigma2 - 1.0-r8.4-bh4
root@vusolo:/usr/bin#


    OE1.6:

    Code
    root@dm800se:~# opkg list-installed|grep 'enigma2 '
enigma2 - 3.2git20121103-r0
task-opendreambox-enigma2 - 1.0-r10
root@dm800se:~#


    Where is here in OE2 version higher than 3.9?
    Thx

    Zitat von m0rphU

    cat /etc/image-version


    OE1.6:

    Code
    root@dm800se:~# cat /etc/image-version
version=0324201211041155
comment=OpenDreambox
target=9
creator=OpenEmbedded <oe@dreamboxupdate.com>
url=http://www.dreamboxupdate.com/
catalog=http://www.dreamboxupdate.com/
root@dm800se:~#


    OE2.0:

    Code
    root@vusolo:/usr/bin# cat /etc/image-version
version=1000201305151438
root@vusolo:/usr/bin#


    How to identified difference?

    Code
    root@dm8000:~# opkg list-installed|grep 'enigma2 '
 enigma2 - 3.999git20140314-r9.0


    here is the 3.9, this is a actual Version.
    OE is not an Enigma version. OE is only the development environment.


    You can not compare VU with DMM Versions. E2 of the VU is based on an E2 version level, as DMM still OE1.6 used. That's ages ago. VU-E2 is based on this old version.


    PS: and this is a Dreambox-Only-Forum :face_with_tongue:

    Einmal editiert, zuletzt von joergm6 ()

    Ok..
    But if you want to write some plugin who will be universal for all platform then you must know exactly is it OE1.6 or OE2.0.
    For now I think that this is best method:

    Code
    detectOE(){
if [ -d "/usr/lib/python2.7" ]; then
	echo "OE2.0 Detected"
	OE="20"
else 
  echo "OE1.6 Detected"
	OE="16"
fi
}
    Zitat von easyyu


    But if you want to write some plugin who will be universal for all platform then you must know exactly is it OE1.6 or OE2.0.


    Generally it is not necessary to know the specific python version. In some cases it may be useful, but only if you use some special functions which are not up-/backward compatible.
    And as joerg already said this has nothing to do with the specific OE platform this is only depending on the used python version.

    Zitat von dhwz


    Generally it is not necessary to know the specific python version. In some cases it may be useful, but only if you use some special functions which are not up-/backward compatible.
    And as joerg already said this has nothing to do with the specific OE platform this is only depending on the used python version.


    Exactly, beacuse the python, because plugin isn't compatible between this two OE!
    And this is the reason why I asked how to recognize OE1.6 vs OE2.0.

    If you distribute closed source, then yes. If it's about the architecture mipsel or mips32el, then you can use "Architecture: all" . A usage of closed source is no protection. This is decompiled quickly, the effort worthwhile not. :face_with_rolling_eyes: