is there a protocol for suggesting the removal of obsoleted(?) packages? i was looking at the recipes for some embedded tools, and noticed:
$ ls recipes/i2c-tools files i2c-tools_3.0.2.bb picodlp-control_0.1.bb i2c-tools_3.0.1.bb picodlp-control read-edid_1.4.1.bb $ in other words, both versions 3.0.1 and 3.0.2 (3.0.2 is current). a recursive grep of the entire checkout reveals: $ grep -r i2c-tools * conf/checksums.ini:[http://dl.lm-sensors.org/i2c-tools/releases/i2c-tools-3.0.1.tar.bz2] conf/checksums.ini:[http://dl.lm-sensors.org/i2c-tools/releases/i2c-tools-3.0.2.tar.bz2] contrib/angstrom/build-feeds.sh: i2c-tools \ recipes/tasks/task-cli-tools.bb: i2c-tools \ recipes/i2c-tools/i2c-tools_3.0.2.bb:SRC_URI = "http://dl.lm-sensors.org/i2c-tools/releases/i2c-tools-${PV}.tar.bz2 \ recipes/i2c-tools/i2c-tools_3.0.1.bb:SRC_URI = "http://dl.lm-sensors.org/i2c-tools/releases/i2c-tools-${PV}.tar.bz2"; $ given the above, it would seem reasonable that version 3.0.1 can be tossed, no? unless there's a compelling reason to keep it around. rday p.s. i can submit a patch if that's all it takes. from what i can see, that just involves removing that single older .bb file. -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ======================================================================== _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
