Very nice but you didn't answer my question in post 15
I didnt answer as i personally dont make .ipk files, there are many that do however.
Very nice but you didn't answer my question in post 15
I didnt answer as i personally dont make .ipk files, there are many that do however.
What would be a nice improvement would be to be able to shrink the database which just seems to get bigger and bigger over time.
Wiz the problem is that making things cross platform isn't that easy from what I've seen and played around with. So the vix guys do what they need to do for vix which is understandable.
What would be a nice improvement would be to be able to shrink the database which just seems to get bigger and bigger over time.
But I thought the whole idea behind the OE-Alliance was that all plugins etc would be compatible across all ranges of boxes that they created images for?
Kind of defeats the purpose of having an OE-Alliance doesnt it?
The OE-Alliance provides a central GIT for all member teams to cherry pick from, but each team is still untimely responsible for their own OE build environment. all ViX plugins are fully OE-A compliant and many other members of the OE-A regularly use these plugins such as OpenATV.
Feck me its like pulling teeth lol
So as i was saying if somebody could create an ipk file from the new crossepg oe-alliance source, we may then be able to try it on non vix images and boxes,
I might come across as stupid at times but I'm usually not, I even surprise myself sometimes ,
Also are OpenATV the same as OpenAAF?
I cant answer questions about .ipk's files as i dont build them. OpenATV is the new name for OpenAAF.
I asked for this feature months and months ago. Glad to see it implemented. Its a v.good feature.
enigma2-plugin-systemplugins-crossepg_0.7.01+git367+7c6b2c8-r1_mips32el
opkg download enigma2-plugin-systemplugins-crossepg
totally forgot about that command in the vix image.
We use essential cookies to make this site work, and optional cookies to enhance your experience.