Seriously: don't send users out of Extras without a big warning - Page 5 - maemo.org

Active Topics

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (9)
to SailfishOS by biketool - 15 hrs, 29 mins ago
[Announce] coderus unrestricted system-ui (297)
to MeeGo / Harmattan by nieldk - 6 days, 20 hrs ago
more...

Page 5 of 5

« First

< Prev

Thread Tools

	Flandry	2009-12-02 , 15:34
	Posts: 1,559 \| Thanked: 1,786 times \| Joined on Oct 2009 @ Boston	#41

Originally Posted by attila77

Just to clear up a few things - as much as I hate the /opt problem, we're talking about dev repos here. There is no guarantee about anything there - it's the wild west. So yeah, stuff should gravitate to optification, but the chief rule is still caveat emptor.

Yes, hence this thread.

AFAIK this problem isn't going to just go away for step 5, either. The maemo6 device will run on the same OMAP3 as N900, and IIRC the 256 MB flash was the biggest option for OMAP3. Even if that is doubled by next year, it's not going to make this a non-issue. Also, you want the rootfs on the faster flash, so that's why it's there...

Since it's a compressed FS this is a bit tricky. There was the idea of the autobuilder inserting a helper field in the debs about the 'real' disk usage of a package (to prevent even considering packages that can't fit), but I don't know what happened to that train of though...

Ran out of steam (well, at least the "userspace" side of it did):
http://talk.maemo.org/showthread.php?t=33654

I actually looked into this a bit when i found out HAM is open, but the atmosphere of discouragement of the idea in that brainstorm thread made me put it on hold, at least until i see how my first submitted patch to HAM is handled (or not). No sense spending time on it if it will never see the light of day.

__________________

Unofficial PR1.3/Meego 1.1 FAQ

***

Classic example of arbitrary Nokia decision making. Couldn't just fallback to the no brainer of tagging with lat/lon if network isn't accessible, could you Nokia?

MAME: an arcade in your pocket
Accelemymote: make your accelerometer more joy-ful

Last edited by Flandry; 2009-12-02 at 15:37.

Quote & Reply |

tpaixao	2009-12-07 , 21:00
Posts: 143 \| Thanked: 99 times \| Joined on Jun 2009 @ Houston	#42

Originally Posted by pycage

The package manager shows it in the details summary.

It does? where? Mine only shows the dependencies, not the repositories they come from.
That would be quite useful, actually

Quote & Reply |

	hypoxic	2009-12-08 , 04:28
	Posts: 23 \| Thanked: 20 times \| Joined on Dec 2009	#43

Originally Posted by tpaixao

It does? where? Mine only shows the dependencies, not the repositories they come from.
That would be quite useful, actually

-choose an app to install
-click 'details' button on confirmation screen
-on 'Summary' tab at the bottom is listed 'Catalog' - this appears to tell what repository the package will be installed from.

however i still like the idea of color coding for non 'safe' packages. red or yellow is very clear and would help to show that what is being chosen needs to have an understanding on possible impact.