Re: openoffice problem prevents desktop task from working on all arches except: i386, powerpc, s390, sparc
Hi Joey,
Joey Hess wrote:
> Rene Engelhard wrote:
> > Didn't I already tell you this on IRC months ago?
> > Well, you added -bin in addition to openoffice.org then, but I guessed
> you
> > knew what you did... To be honest, I wonder why you come up with this
> > *now*...
>
> I don't keep a record of things people tell me on IRC, TBPH.
>
> OOo was not a part of the desktop task months ago, and months ago tasks
> were installed in a slightly more robust way that hid this problem. I
> also didn't have a machine in an affected architecture to test until 2
> days ago.
OOo *was* part of the tasks months ago if you mean your latest drastic
change in the task structure. That change was months after I told you on IRC
about the problem and you added openoffice.org-bin in addition to
openoffice.org to the task. And we discussed it, I didn't just tell you.
Anyway, I didn't want to insult you I just remembered we talked about that
on IRC and wondered why the problem appeared now again...
> > #2 is planned _after sarge_, openoffice.org will be i386 powerpc s390
> sparc
> > arm (former -bin) and openoffice.org will mutate into -common. I am not
> sure
> > whether it will be done with the first 1.1.3 upload but it is in my mind
> and
> > the wish already is in the BTS:
> >
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252125
> >
> > -help-* and -l10n-* *are* architecture-independent, it would be
> senseless
> > to make them architecture-dependent and increase build time for
> binary-only
> > builds and mirror space - OOo is big enough already and with the 11! new
> > binary packages which are planned (IIRC 5 of them new language packs and
> 2
> > other arch-indep packages) it will be even bigger....
> >
> > It is not feasible to do inside the sarge timeframe although some people
> > (including you probably) would like it.
>
> This leaves me only two options, I can entirely remove all OOo stuff
> from all tasks, or I can remove all arch all stuff from all tasks,
This would be the most ba option of all IMHO. There is and was a reason that
OOo is included in the desktop task....
> leaving the main program.
Leaving only the main program is the solution which would be really bad for
our clueless users having no plan and wondering what to do to get
$foo_language ui, help. More importantly: spellchecking. We got questions
about that often...
Why don't you just ignore it? Users on !(i386, powerpc, s390, sparc) IMHO
should already know what they are doing (most clueless people already use
i386/powerpc or something like that). Because they have clue they could
figure out that OOo isn't available for them (it maybe will be for arm after
sarge) and can install the desktop stuff themselves
OTOH I see that this doesn't fit into the "stable" category, which indeed is
bad...
Or - this is the best but most work-intensive solution - figure out a system
where this cam't/won't happen..
But well, that's just my 0.02 EUR.
Regards,
René
Reply to: