2009/11/26 Ionut Biru :

always do pacman -Syu if you refresh your database(pass -y to pacman). so do pacman -Syu and then pacman -S libwebkit

Is this going to upgrade every package on my system? -- Samuel Baldwin - logik.li

On 11/27/2009 12:17 AM, Samuel Baldwin wrote:

2009/11/26 Samuel Baldwin:

...

Is this going to upgrade every package on my system?

Uh, yeah, is there any other way to do this without installing 410 packages?

nope. this is the only supported way -- Ionut

2009/11/26 Ng Oon-Ee :

Arch is a rolling release. If you don't want to regularly update your packages, things will break eventually.

Rather, things tend to break when upgrading; I can't imagine wanting the latest version of all the software I'm running. I don't really have any other options, though. -- Samuel Baldwin - logik.li

On Thu, 2009-11-26 at 17:51 -0500, Samuel Baldwin wrote:

2009/11/26 Ng Oon-Ee :

...

Arch is a rolling release. If you don't want to regularly update your packages, things will break eventually.

Rather, things tend to break when upgrading; I can't imagine wanting the latest version of all the software I'm running. I don't really have any other options, though.

I'm not trying to be snarky, though it'll come across as that a bit. If you're not keeping the system reasonably up to date (without 410 packages waiting in the background), you should really look for another distro. The inter-dependence can be quite strong, here. Small (relatively) changes in the APIs of certain libraries can break older versions of user-interaction programs. Say the packages A and B depend on library M, but you only upgrade A. If A needs a newer version of library M, that will be pulled in too. On an API update (even worse, ABI update), this would break B. In short, keep updated. Doesn't need to be daily, but at the very very least 1-2 times a month. On Fri, 2009-11-27 at 00:00 +0100, fons@kokkinizita.net wrote:

On Fri, Nov 27, 2009 at 06:48:37AM +0800, Ng Oon-Ee wrote:

...

Arch is a rolling release. If you don't want to regularly update your packages, things will break eventually.

You must be the Ng Oon-Ee I bumped into today on Linux Audio User ? :-) :-)

Ciao,

The very same =)

On Thu, 2009-11-26 at 19:05 -0500, Samuel Baldwin wrote:

2009/11/26 Ng Oon-Ee :

...

In short, keep updated. Doesn't need to be daily, but at the very very least 1-2 times a month.

Fair enough, I'm going to start doing that. And no, it didn't come off as snarky, but rather objective; I had considered looking around for something else once this started, but it'd be less hassle for me to just keep things up to date like I should.

Yes, I believe that would be the case. Good practice is just before updating to browse through the last 2 or 3 pages of BBS postings to see if there's complaints on packages/software you use, as well as watch the front page. And this ML of course.

On Thu, Nov 26, 2009 at 05:17:56PM -0500, Samuel Baldwin wrote:

2009/11/26 Samuel Baldwin :

...

Is this going to upgrade every package on my system?

Uh, yeah, is there any other way to do this without installing 410 packages?

I know the discussion shifted to the daily preach about the importance of upgrading. But to answer this very question: Yes you can. You grab libwebkit(and any missing dependencies) from ABS(or SVN) and build them. If everything builds successfully with the current packages you have in your system, then you are good to go. Having said that, webkitgtk(Upstream name) develops fast. They have 1.1.15.x stable releases and 1.1.16.x releases. Some browsers(e.g Epiphany) develop for a not yet released version (using SVN trunk or GIT API). Long story short, you would need updated packages If you want the latest and greatest from a webkit-based browser.