Hi,
I'm currently working on opkgc so it becomes able to package new apitests
struture.
now, all .apt and .apb apitests for opkgs are stored in
/usr/lib/oscar/testing/apitests.d
those files can call real scripts stored in /usr/lib/oscar/testing/tests.d
Finally, a directory containing other data (used for tests or to be copied to
clients for tests (like mpi tests) are stored in
/usr/lib/data/testing/data/<pkg_name>).
So an opkg content is the following for the package "foo":
=> opkg-foo: # The api part package
/usr/lib/oscar/package/foo/config.xml
/usr/lib/oscar/package/foo/api-post-clientdef
/usr/lib/oscar/package/foo/api-post-deploy
/usr/lib/oscar/package/foo/api-post-image
/usr/lib/oscar/package/foo/api-post-install
/usr/lib/oscar/testing/apitests.d/foo_config.apb
/usr/lib/oscar/testing/apitests.d/foo_validate.apb
/usr/lib/oscar/testing/apitests.d/*.apt # used by above apitest batch scripts
/usr/lib/oscar/testing/tests.d/* # called by above *.apt apitest test scripts
(optional)
/usr/lib/oscar/testing/data/foo # used by above tests (can also be copied to
oscartst home for remote tests). this directory is owned by package while
apitests.d and tests.d are not)
/usr/share/doc/foo* # The package doc
=> opkg-foo-server: # The server part package
/usr/lib/oscar/package/foo/server-post-install
=> opkg-foo-client: # The client part package
/usr/lib/oscar/package/foo/client-post-install
RPM side is working fine. (but will need work to harmonize between deb and rpm)
DEB side was broken and is still broken.
- DEB side was packaging *{pre|post}-{un,}install scripts as package pre/post
install/uninstall script which is wrong as those scripts are meant to be run by
wizard. More over, there are no pre-install scripts and no uninstall scripts in
svn.
Server and client post install were run by the package at install time (wrong)
and re-run by wizard ( normal behaviour) (thus ran twice).
=> Work to do:
- use .install files (for deb and rpm (used by %file sections in rpm (more
simple than generating them in the template and permit to have a clean %doc)
- use make install in spec file instead of generated manual copy of files.
- update deb rules so it uses dh_makeinstall (no more install from opkgc.
Thus we are sure that rpm and deb side will use the same install)
- no more pre/post in deb side (same as rpm). scripts are not package
post-install, they are wizard steps post-install which is different as they can
be run several times and when run, they are once in a raw.
Best regards,
Olivier.
--
Olivier LAHAYE
CEA DRT/LIST/DIR
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel
