1748 replies to this topic

[Persian Prince]

src and dev packages have different meanings and python is designed for compiling when running, but if you start ignoring such enigma2 design principles and feel comfortable...

 

As I'm pretty sure that our friends are NOT shipping most of their Plugins without py just to save space and avoid compilation this move is simply suspicious - especially together with such arguments. If DMM would do such a move they would be grilled once more

 

But I'm just pointing out the personal opinion of a dumb person which doesn't understand the enigma2 community and Open Source.

 

And actually you are not splitting you are multiplying keeping different CPU architectures in mind.

 

why should we compile py files on the box when we can do it with a compiler machine ? i don't agree with you at all

if you wanna change something simply install the -src package , there is no need to install these kind of files for normal users

feed will provide the sources not the box itself

other devs could publish their plugins with -src beside them and i think it's not PLi's duty to consider such things

 

DMM removed the enigma2 sources and you wanna compare this with splitting ? really ?

 

i think removing and splitting has different meanings in my dictionary

 

btw i'm not a PLi member and i can just sit and drink when i have extra time but i wanna contribute as a friend

 

they can revert the commits if they want

[Lost in Space]

I simply don't like if somebody decideds for me what I need.

 

And there might be others seeing it the same way.

 

But it is not my decision what PLi does.

 

But from now on I hereby FORBID to ship any of MY Plugins with compiled python!

 

But this is OT here, I'm sorry.

Edited by gutemine, 18 April 2013 - 20:55.

[pieterg]

But from now on I hereby FORBID to ship any of MY Plugins with compiled python!

Ah, introduce more limitations, that's the spirit

[Rob van der Does]

Euuuhhh..... if a plugin without .pyo-files has been installed, OPKG won't remove the files that E2 has compiled. Hence the plugin will have to be removed by hand.

Surely that can't be the idea?

[ims]

Would not be better repair dmm's e2 images to next night build ?

[Lost in Space]

It is not only that who removes what problem, it is also much more fun for the plugin devlopers to analyze crashdumps and supprt their plugins.

 

Hence I'm simply forbiding shipping my stuff this way without the python sources - like it or not.

 

YOU are not supporting them, are you ?

 

And you are simply violating the license rules of a lot of plugins that clearly state their credits and the license has to be shipped as it is togetherwith the plugin - and this is very hard to read in a pyo - and an extra package with the sources is then already a violation.

 

If you are not even understanding the implications of what you are doing then you should not do it - I'm sorry for such hard words.

Edited by gutemine, 18 April 2013 - 22:01.

[Persian Prince]

so ubuntu is violating everything

[gorski]

Luckily, not all developers are sold souls...

[theparasol]

Its always nice to see difference  in approaches and discussion about the "best" approach.

I dont have an opinion since I dont know all the ins and outs about certain choices but I'm always openminded to learn from you guys!

My python skills are based on reading/learning from sourcecode and searching for right commands to change (minor) things so I would be glad that the source is always shipped.

I dont care about "startup" time of enigma2 as long as it isnt taking 15 minutes.

[Persian Prince]

@pieterg

 

DMM has

# Inject the /boot partition into /etc/fstab. At image creation time,
# this is done by IMAGE_CMD_jffs2.nfi (image_types_nfi.bbclass).
pkg_postinst_base-files() {
if [ -z "$D" ]; then
	ROOT='\<root=/dev/mtdblock3\>\|\<root=ubi0:rootfs\>'
	if grep -q $ROOT /proc/cmdline && ! grep -q '\s\+/boot\s\+' /etc/fstab; then
	       printf '/dev/mtdblock2\t/boot\t\tjffs2\tro\t\t\t\t0 0\n' >> /etc/fstab
	fi
	if grep -q '/dev/ubi0_1' /proc/mounts && ! grep -q '\s\+/data\s\+' /etc/fstab; then
	        printf '/dev/ubi0_1\t/data\t\tubifs\trw\t\t\t\t0 0\n' >> /etc/fstab
	fi
fi
}

in base-files_3.0.14.bbappend , do we need it ?

[pieterg]

no, not really. As we don't keep the boot partition mounted.
We should make a workaround in the kernel-image / bootlogo postinst hooks though.

[pieterg]

We should make a workaround in the kernel-image / bootlogo postinst hooks though.

actually, no need, as the boot partition is still jffs2 (the secondstage loader does not support UBI)

[Persian Prince]

ok

 

also tonight i'll send some merge requests for Open PLi 2.1 like dm800 driver update and some tweaks for less image size

Edited by Persian Prince, 18 April 2013 - 23:24.

[Persian Prince]

new merge requests for both OEs sent

 

apply what you want

[Persian Prince]

i think your build stoped on dm7020hd

 

maybe it's good to move all dreambox models after vuplus in the build script

 

also we have dm7020hdv2 and we can have something like http://git.opendream...392dd;hb=master

 

for it , it needs

require conf/machine/include/dreambox-nand-1024mb-2k.inc

and for Makefile : http://git.opendream...33eb11a41abbcc4

[Persian Prince]

i sent another pull request here : https://github.com/E...enplugins/pulls

 

it will reduce all packages specially Open WebIF also you should update e2openplugins submodule after merging (for both OEs)

 

up to you

Edited by Persian Prince, 19 April 2013 - 04:32.

[malakudi]

normal users only need compiled packages with pyo files not with py files (sources)

 

it will help to reduce the image size and prevent compiling on the box

 

"Normal" users are now confused by seeing two packages in plugin management, one normal and one with -src in the name. And if they install -src, when they remove it the plugin is still installed because the pyo files are not deleted. src package should have both py and pyo or a proper uninstall script. How much space you think you are saving by removing high compressable text files? 1%?

 

I think what you did is wrong and I suggest reverting it.

Edited by malakudi, 19 April 2013 - 09:11.

[littlesat]

Normal" users are now confused by seeing two packages in plugin management, one normal and one with -src in the name

As far I know this is fixed....

Even for enigma2 we have a -src ipk.... so why not for plugins?

Edited by littlesat, 19 April 2013 - 09:14.

[Erik Slagter]

<sorry not relevant>

Edited by Erik Slagter, 19 April 2013 - 09:14.

[pieterg]

I don't think it's a big issue, we've been doing this for enigma2 as well, for years.
OK, mostly to make things fit on the dm7025, which could use every single bit of size reduction.
But some other dreambox models have very limited flash as well, which, especially now with UBI, will become an issue for several users.

Of course, for a few python files, you do not save very much.
But if I look at enigma2-src for instance, if I install it my rootfs changes from

Filesystem           1K-blocks      Used Available Use% Mounted on
ubi0:rootfs             223520     74444    149076  33% /

to

ubi0:rootfs             223520     71020    152500  32% /

Which is ~3.4 MB's, even after compression.

Agreed, for plugins with just a few py's it's probably not worth the hassle to try and split every single package.
But also, I don't consider this such a big issue that we should revert it.

(The issue of seeing -src packages in the plugin list should have been addressed in todays build by the way)