Dear all,
I've worked on oscar-packager along the day, and finaly fixed most of the build
process.
What works:
now, rpm can be build in the following cases: (decreasing priority)
I) from SVN (/etc/oscar/oscar-packager/included_unstable.cfg)
1/ build.cfg + package.cfg(src.rpm) + deps
2/ build.cfg ° package.cfg(tarball and other materials)
3/ only a spec file either in ./rpm/ or ./
4/ build.cfg + spec file
5/ build.cfg + Makefile with rpm: rule
6/ Makefile only with rpm: rule
II) from src.rpm (/etc/oscar/oscar-packager/included_unstable.cfg)
III) from tarball (/etc/oscar/oscar-packager/included_unstable.cfg) provided
that there is a spec file in the archive (NO TESTED YET)
What does not work:
If package is built from prepare_prereqs (using the build.cfg)
then, if it fails it seems that /etc/oscar/oscar-packager/.oscar_pkgs is not
updated.
In some situation above (different build types) the failed build are not
reported.
Regards,
PS: oscar-packager command parsing needs improvement:
oscar-packager --all --force unstable
or
oscar-packager --all --force torque unstable
does not trigger any error and tries to build the --force packages which does
not exists and there is no errors.
Olivier.
--
Olivier LAHAYE
CEA DRT/LIST/DCSI/DIR
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel
