5,705
edits
Changes
Jump to navigation
Jump to search
Line 89:
Line 89: − +
Platform Team/Package Management System (view source)
Revision as of 23:26, 9 July 2010
, 23:26, 9 July 2010→Regular workflow
* options for distributors:
* options for distributors:
** If it is an OBS-based distribution, there is no need for any packaging-related work at all, just link/branch the activity to your distribution project.
** If it is an OBS-based distribution, there is no need for any packaging-related work at all, just link/branch the activity to your distribution project.
** Reuse the activity spec file to build native packages on non-OBS build farms. Most likely, the resulting packages will not conform to all the requirements for inclusion in an official repository, but this feature could still be useful when strong packaging rules are not required, e.g., in various Sugar/edu derivates like SoaS or USR.
** Reuse the activity spec file to build native packages on non-OBS build farms. Most likely, the resulting packages will not conform to all the requirements for inclusion in an official repository, but this feature could still be useful when strong packaging rules are not required, e.g., in various Sugar/edu derivates like Trisquel-edu, SoaS or USR.
** Using the sources tarball generated by the {{Code|0sugar dist}} command, and information about dependencies from the spec file, create a regular package for any particular GNU/Linux distribution.
** Using the sources tarball generated by the {{Code|0sugar dist}} command, and information about dependencies from the spec file, create a regular package for any particular GNU/Linux distribution.