[maemo-developers] Icons are just a few bytes, right ?

From: john.beattie at accenture.com john.beattie at accenture.com
Date: Fri Mar 12 14:43:42 EET 2010
From: maemo-developers-bounces at maemo.org [mailto:maemo-developers-bounces at maemo.org] On Behalf Of Attila Csipa
Sent: 12 March 2010 12:29
To: Marius Vollmer
Cc: maemo-developers at maemo.org
Subject: Re: Icons are just a few bytes, right ?

On Friday 12 March 2010 12:42:11 you wrote:
> From all the 
> available versions of a package, apt selects one upfront as the
> candidate and then sticks with that.  The only decision it makes is
> between installing that candidate version, keeping the version you have
> already installed, or removing the package altogether.  It will not
> reconsider which version should be the candidate based on dependencies
> between packages.

I'm talking about a scenario when the application has an 'older than' 
dependency (often in combination with '|'), which apt (and HAM) *will* 
honour. So if app A has a libfoo << 2.0 dep, app B has libfoo >> 1.0, and 
there is currently a libfoo 1.5 in the repo, both A and B are installable. If 
you upload libfoo 2.5, however, and 1.5 gets automatically archived, app A is 
no longer installable (even though it could have been if you kept both 
versions of libfoo). Not a common case, I admit, just saying one has to be 
careful when removing packages from repos.

Regards,
Attila



This thread includes quite a bit of useful insight into the general behaviour
of apt.   Does anybody have a reference for a description of apt's behaviour?
Ideally, a comprehensive specification.

I don't mean the man page, that only gives the arguments to apt-get or
whatever.  What I mean is a description of what, say, 

# apt-get install pkg

does.  More exactly, what it does relative to a given sources.list.

Regards,
John



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.
More information about the maemo-developers mailing list