[prev in list] [next in list] [prev in thread] [next in thread]
List: opensolaris-desktop-discuss
Subject: Re: [desktop-discuss] CD Space analysis and recommendations
From: Peter Korn <Peter.Korn () Sun ! COM>
Date: 2008-09-15 19:31:52
Message-ID: 48CEB828.5070905 () sun ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Andras,
I'll leave it to Willie Walker to provide additional detail here as
needed.
Fundamentally, folks are working hard to fix this bug in the
packagemanager GUI. Separately, the question of whether accessibility
is on/off by default for *all* users is distinct from whether an
individual user can turn it on for *their* default use so that it is on
whenever they log in. Or in this case, when they go to install their
desktop (which means it must be on the LiveCD). If they cannot have an
accessible desktop until they have downloaded additional packages, then
we have a rather serious chicken/egg problem. As has been pointed out
in that (and/or perhaps related) thread(s), the command line is also an
option for users who want to download additional packages (and need
accessibility support in the case that this bug isn't fixed).
Regards,
Peter
> check this thread:
> http://mail.opensolaris.org/pipermail/jds-review/2008-September/003151.html
>
> On Mon, Sep 15, 2008 at 9:37 PM, Peter Korn <Peter.Korn@sun.com> wrote:
>
>> Andras,
>>
>> laca, i read in a different thread that a11y isn't enabled by default
>> so why to include that packages ?
>>
>>
>> Accessible install is part of what we're planning for 2008.11. The blind
>> (or whatever) user can turn accessibility on with a keyboard gesture and
>> have a talking install from their talking desktop that they've booted to
>> from the LiveCD. We really can't have that work if we are missing the
>> accessibility packages on the LiveCD...
>>
>>
>> Regards,
>>
>> Peter
>>
>> On Mon, Sep 15, 2008 at 10:17 AM, Laszlo (Laca) Peter
>> <Laszlo.Peter@sun.com> wrote:
>>
>>
>> Dave,
>>
>> This is gonna be depressing, but the size of the GNOME packages
>> with the 2.24 update is expected to increase by about 11MB
>> (compressed!) Attached is a StarOffice spreadsheed (and a pdf
>> export for easier reading).
>>
>> It looks likes like firefox3 accounts for almost 1/3 of the
>> size increase.
>>
>> There is 1 new required package, SUNWlibtasn1 but we should
>> also consider SUNWespeak and SUNWgnome-a11y-speech-espeak for
>> better accessibility support.
>>
>> Laca
>>
>> On Wed, 2008-08-20 at 15:10 -0400, Dave Miner wrote:
>>
>>
>> Filters are not yet implemented.
>>
>>
>>
>> One possible outcome here is that we ask IPS to kick up the priority of
>> implementing filters to help solve the problem.
>>
>> Anyway, thanks for digging in, Laca. We can certainly ensure that stuff
>> that's split out into separate packages stays out. For the moment, no
>> need to do anything, I'm waiting on some data about l10n and other
>> things before putting together revised recommendations. Are there any
>> other significant changes in the 2.23.x packages that we need to account
>> for?
>>
>>
>> _______________________________________________
>> desktop-discuss mailing list
>> desktop-discuss@opensolaris.org
>>
>>
>>
>>
>>
>>
>
>
>
>
[Attachment #5 (text/html)]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Andras,<br>
<br>
I'll leave it to Willie Walker to provide additional detail here as
needed. <br>
<br>
Fundamentally, folks are working hard to fix this bug in the
packagemanager GUI. Separately, the question of whether accessibility
is on/off by default for *all* users is distinct from whether an
individual user can turn it on for *their* default use so that it is on
whenever they log in. Or in this case, when they go to install their
desktop (which means it must be on the LiveCD). If they cannot have an
accessible desktop until they have downloaded additional packages, then
we have a rather serious chicken/egg problem. As has been pointed out
in that (and/or perhaps related) thread(s), the command line is also an
option for users who want to download additional packages (and need
accessibility support in the case that this bug isn't fixed).<br>
<br>
<br>
Regards,<br>
<br>
Peter<br>
<br>
<blockquote
cite="mid:56dc2e760809151159r389d7634j1aa0cfc385ceaf27@mail.gmail.com"
type="cite">
<pre wrap="">check this thread:
<a class="moz-txt-link-freetext" \
href="http://mail.opensolaris.org/pipermail/jds-review/2008-September/003151.html">http://mail.opensolaris.org/pipermail/jds-review/2008-September/003151.html</a>
On Mon, Sep 15, 2008 at 9:37 PM, Peter Korn <a class="moz-txt-link-rfc2396E" \
href="mailto:Peter.Korn@sun.com"><Peter.Korn@sun.com></a> wrote: </pre>
<blockquote type="cite">
<pre wrap="">Andras,
laca, i read in a different thread that a11y isn't enabled by default
so why to include that packages ?
Accessible install is part of what we're planning for 2008.11. The blind
(or whatever) user can turn accessibility on with a keyboard gesture and
have a talking install from their talking desktop that they've booted to
from the LiveCD. We really can't have that work if we are missing the
accessibility packages on the LiveCD...
Regards,
Peter
On Mon, Sep 15, 2008 at 10:17 AM, Laszlo (Laca) Peter
<a class="moz-txt-link-rfc2396E" \
href="mailto:Laszlo.Peter@sun.com"><Laszlo.Peter@sun.com></a> wrote:
Dave,
This is gonna be depressing, but the size of the GNOME packages
with the 2.24 update is expected to increase by about 11MB
(compressed!) Attached is a StarOffice spreadsheed (and a pdf
export for easier reading).
It looks likes like firefox3 accounts for almost 1/3 of the
size increase.
There is 1 new required package, SUNWlibtasn1 but we should
also consider SUNWespeak and SUNWgnome-a11y-speech-espeak for
better accessibility support.
Laca
On Wed, 2008-08-20 at 15:10 -0400, Dave Miner wrote:
Filters are not yet implemented.
One possible outcome here is that we ask IPS to kick up the priority of
implementing filters to help solve the problem.
Anyway, thanks for digging in, Laca. We can certainly ensure that stuff
that's split out into separate packages stays out. For the moment, no
need to do anything, I'm waiting on some data about l10n and other
things before putting together revised recommendations. Are there any
other significant changes in the 2.23.x packages that we need to account
for?
_______________________________________________
desktop-discuss mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:desktop-discuss@opensolaris.org">desktop-discuss@opensolaris.org</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>
_______________________________________________
desktop-discuss mailing list
desktop-discuss@opensolaris.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic