Re: Autopackage?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Autopackage?
by Christian Loose on Friday 16/Sep/2005, @06:17

I agree with almost all you have said, but I wouldn't limit the scope of klik as much as you did. I think it's also interesting for end-users.

Just a few use-cases, where I think that klik would be useful:

a) You want to try-out a new version of an application without removing the current installation.
b) You want to try-out a new application but you want to make sure that you can remove it cleanly without disturbing the rest of the system.
c) You are on a multi-user machine and really want to use this one application that the sysadmin doesn't care about. :)

Besides the amount of duplicate libraries really depends on the definition of the base libraries. When you see Qt and kdelibs as part of the base system than the duplication is IMHO negligible.

Related Links

·   Articles on KDE Tweak of the Week
·   Also by Christian Loose
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Autopackage?
by Quintesse on Friday 16/Sep/2005, @06:51

How about that application where nobody has bothered yet to make a package for?
Or just because it's so damn easy to click on a link and start using the app?

[ Reply To This | View ]

Re: Autopackage?
by Christian Loose on Friday 16/Sep/2005, @07:08

Of course! My list wasn't meant to be exhaustive. :)

[ Reply To This | View ]

Re: Autopackage?
by Andreas Hennig on Friday 16/Sep/2005, @07:16

You're totaly right... my comment was not so much about what klik can do... but rather about how Autopackage complements Klik or vise-versa.

Scenario 1. I am the Admin

I can even think of a situation where I would use klik to test, check out the feature set or just generally check out a new tool I am thinking of deploying, and then (assuming both klik and autopackages are available... would be nice) once I want to deploy it for the rest of the users, I'd just get an autopackage and install globally, which would give me a few other advantages (as mentioned in earlier post). Or get the rpm, deb or whatever the native package format is.

Scenrio 2. I am just Joe User (or Andi user in my case :)

I want to run a tool my Admin does not have available, and probably won't provide... I get the Klik package and I am done, or I can get the Autopacke which also works, BUT: More than likely though, with me being one of those guys who likes to carry everything with Him (yes, I got a notebook... but the battery is dead, the powersupply is dying, I live in South America and got married recently - i.e. I can't afford a new one), I'd just put the Klik package on my USB stick and carry the tool with me... ;) Can't do that with Autopackage...

So, really In my earlier post I was just trying to clarify some more the usage of Autopackage (which is what I know more about) and not as much to explore the multiple uses of Klik.

I think there is some overlap in possible usage cases, but I still think that they are sufficiently different that a developer might want to publish binaries of all builds (nightly, alpha, beta, rc and final) with Klik and then maybe only publish final builds or maybe beta, rc and finals with Autopackage. I believe it's definitely not an either - or type scenario, but rather a matter of using the right package type for the right job and/or target audience.

Cheers.

[ Reply To This | View ]

Re: Autopackage?
by Taj Morton on Friday 16/Sep/2005, @07:53

<blockquote>Can't do that with Autopackage...</blockquote>
You can create sealed installers with Autopackage, as well as stick the Autopackage support code on a USB drive, and then you have a stand-alone Autopackage. :)

Or maybe I completely missed what you meant. :)

--
Taj

[ Reply To This | View ]

Re: Autopackage?
by Andreas Hennig on Friday 16/Sep/2005, @09:20

Taj,

thanks for correcting me... that's exactly what I meant and I was wrong. That's why I sent a message to the Autopackage mailing list asking everyone to come over and join in the discussion, so the developers themselves would comment on Autopackage and correct any missrepresentation on my part.

Great to see you guys are joining in! You are the ones qualified to talk about Autopackage!! I just try and spread the word, though my understanding might not be complete.

Thanks!!

Andreas

[ Reply To This | View ]

Re: Autopackage?
by Andreas Hennig on Friday 16/Sep/2005, @09:40

[ Reply To This | View ]

Re: Autopackage?
by Andreas Hennig on Friday 16/Sep/2005, @10:05

[ Reply To This | View ]

Re: Autopackage?
by Taj Morton on Friday 16/Sep/2005, @07:50

Autopackage can do c). As for a and b, parallel-installs are slated for 1.1, but they're not implemented yet.

Patches welcome!

--
Taj

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I'm holding out for a computer interface that plugs directly into my cerebral cortex." -- Sirtaj Singh Kang
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.