I thought if I did that, then I it would download all the experimental packages and update everything to experimental. Is that not the case?

Thanks for your responses.

oddball

Post subject:Posted: 01.10.2010, 08:47

Joined: 2010-09-11
Posts: 109
Location: Skåne, Sweden
Status: Offline

goofythekiller wrote:

I thought if I did that, then I it would download all the experimental packages and update everything to experimental. Is that not the case?

Thanks for your responses.

Yes, can someone explain that. I thought to install something from experimental you activate the experimental repository and then do apt-get update, install the app you want from experimental and then deactivate the experimental repository. So why shall we do it like slam shows us, and if we do and have experimental repository activated will it not install gnash from experimental also? Please explain!

slam

Post subject:Posted: 01.10.2010, 09:30

Team Member

Joined: 1970-01-01
Posts: 607
Location: w3
Status: Offline

Experimental is no complete distribution, but just a repo to store versions of some apps and libs in "experimental" state. So, if you need a single package from there, you activate the repo, and do

Code:

apt-get update && apt-get install packagename/experimental

or, for packages with depending other libs/apps in experimental

Code:

apt-get update && apt-get install packagename -t experimental

You may de-activate experimental after that, but it also does no harm to leave it active. Reason: Any installation of other packages (or dist-upgrades) without telling apt explicitly to pull from experimental, will ignore the experimental repository.
Greetings,
Chris

Thank you for making this more understandable and clear slam, very good!

Lanzi

Post subject:Posted: 01.10.2010, 15:57

Joined: 2010-09-11
Posts: 126
Location: Hessen
Status: Offline

@Slam

Quote:

You may de-activate experimental after that, but it also does no harm to leave it active. Reason: Any installation of other packages (or dist-upgrades) without telling apt explicitly to pull from experimental, will ignore the experimental repository.

so no pinning in /etc/apt/preferences is necessary?
I was always confused why we don't have a 'preferences' file.

Experimental is no complete distribution, but just a repo to store versions of some apps and libs in "experimental" state. So, if you need a single package from there, you activate the repo, and do

Code:

apt-get update && apt-get install packagename/experimental

or, for packages with depending other libs/apps in experimental

Code:

apt-get update && apt-get install packagename -t experimental

You may de-activate experimental after that, but it also does no harm to leave it active. Reason: Any installation of other packages (or dist-upgrades) without telling apt explicitly to pull from experimental, will ignore the experimental repository.
Greetings,
Chris

I would like to ask a little more about above:

If I have installed something like "application A" from experimental and do a d-u, where will an updated version of "application A" be pulled from, sid or experimental? In other words, will apt "remember" that "aplication A" is from experimental and look for an updated version there?

blackhole

Post subject:Posted: 10.10.2010, 16:37

Joined: 2010-09-12
Posts: 110

Status: Offline

Quote:

If I have installed something like "application A" from experimental and do a d-u, where will an updated version of "application A" be pulled from, sid or experimental?

Only from sid, when the version will be higher than that installed from experimental