We must be carefull when building or modifying code in opkg scripts.
Geoffroy did started a migration from oscar/trunk/packages/<package> to
pkgsrc/<package>/trunk/ in order to move opkg outside oscar core tree and thus
avoid doing an oscar release when some opkg has been updated.
Unfortunately, this migration was not finished and thus the code is sometimes
present at two places.
What is relevant is the location pointed by
/etc/oscar/oscar-packager/core_opkgs_unstable.cfg
For example opkg-oda{,-client,-server} are built from oscar/trunk/packages/oda.
There is also pkgsrc/oda/trunk/ that has all the necessary stuffs to build the
opkg, but it is not used.
For the moment, I'll just check if there are any differences and duplicate the
code. Later, we'll need to migrate all code to pkgsrc (finish the change) and
update the packager accordingly. then remove the oscar/packages content.
Regards,
Olivier.
--
Olivier LAHAYE
CEA DRT/LIST/DM2I/DIR
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel
