Discussion:
[CSSU] how to include rewrites of closed blobs
Christian Ratzenhofer
2012-05-11 09:11:43 UTC
Permalink
Coming monday (14.05) we will have an irc meeting in #maemo-ssu on
freenode @ 18:00 UTC

Target of the meeting is to decide on a way how we handle rewrites
within cssu, and how new ones should be added.
Anybody is free to join the discussion!

Christian
Andrew Flegg
2012-05-11 09:27:36 UTC
Permalink
On 11 May 2012 10:11, Christian Ratzenhofer
Coming monday (14.05) we will have an irc meeting in #maemo-ssu on freenode
@ 18:00 UTC
Target of the meeting is to decide on a way how we handle rewrites within
cssu, and how new ones should be added.
A previous discussion can be seen at:

http://mg.pov.lt/maemo-ssu-irclog/%23maemo-ssu.2012-05-07.log.html#t2012-05-07T15:08:09

My position is that the CSSU exists to make possible for the average
user things which only Nokia could previously do (such as
upgrades/bugfixes to hildon-desktop & Modest). If something can be
installed via Extras, it should be. If it's a fully functional
rewrite, an additional package can be used to swap the .desktops etc.
This means users can have the choice between, and compare
side-by-side, the original and the rewrite. This additional "bridging"
package *might* require the CSSU. If so, maybe it should be in a
separate repo, a "CSSU Extras" if you will.

See you Monday!

Cheers,

Andrew
--
Andrew Flegg -- mailto:***@bleb.org  |  http://www.bleb.org/
Joerg Reisenweber
2012-05-11 12:26:14 UTC
Permalink
thanks Andrew, for clarification :-D
100% agree.

I just like to add we already have some apps that are no rewrites but clearly
depend on CSSU (orientation lock applet, CSSU-tweaker...) and thus also should
live in that repo CSSU-extras (or whatever path we choose to implement the
concept)

cheers
jOERG
(IRC: DocScrutinizer)
Christian Ratzenhofer
2012-05-15 23:33:41 UTC
Permalink
For those who couldn't attend the meeting:

We decided to introduce / work on a deployment system, which allows the
user to choose for each and every component.

It's made up of 3-4 packages.

#1 is the nokia package, this is not going to be shipped from the cssu
repo, but will be there as always in the nokia ssu repo
#2 is the rewrite package, this is going to live within the cssu repo
and will conflict with #1 and #3
#3 is a helper package, it has no real content, but depends on #1, it
also conflicts #2.
It is needed because most (all) nokia packages are not in one of the
visible user/* sections.

#4 is only existing where appropriate, and will be a package that
installs the rewrite side by side to the nokia package, ie. the
calculator could have such a package.

All those packages (except for #1) will go into a new component inside
the cssu repo, which has the name replace (existing ones are free and
non-free).
Though for this to work we have to adjust the
hildon-application-manager, because currently it just errors out if one
wants to install a conflicting package.
Thus it might take some time before we see any of this in action.

Christian

Loading...