Linspire Standardizes Software Installation Across Linux Distributions
This is a multi-part message in MIME format. |
|
|
Comments (54)
34 earlier comments in the full thread.
> In fact, I think everyone on this list should root for the Bears, and their quarterback, Rex Gr OSS man.
Well, I'll never forgive the franchise for the way they treated Baltimore, so while I won't root for the Bears, I'll definitely be rooting against the Colts.
>Not even that is true. First-time moms almost always need a bit of coaching to learn how to nurse their babies.
TC, the mom's aren't the ones using the nipple interface. They're the ones providing it. What you're pointing out is that taking care of the equipment providing an interface is usually harder than using said interface. I think everyone here can agree on that.
> That must have been said by a "stereotypical" Linux developer.
I believe it was a doctor, but my memory isn't certain on the matter.
> That's what meta packages are for....
Agreed, but I think what Dino is saying in that regard is that meta packages are severly under-utilized, and that most of the details presented to the end user should be in the form of easily understood meta packages.
Well, I'll never forgive the franchise for the way they treated Baltimore, so while I won't root for the Bears, I'll definitely be rooting against the Colts.
>Not even that is true. First-time moms almost always need a bit of coaching to learn how to nurse their babies.
TC, the mom's aren't the ones using the nipple interface. They're the ones providing it. What you're pointing out is that taking care of the equipment providing an interface is usually harder than using said interface. I think everyone here can agree on that.
> That must have been said by a "stereotypical" Linux developer.
I believe it was a doctor, but my memory isn't certain on the matter.
> That's what meta packages are for....
Agreed, but I think what Dino is saying in that regard is that meta packages are severly under-utilized, and that most of the details presented to the end user should be in the form of easily understood meta packages.
Quoting:What you say about dependencies is absolutely correct, and something I have wanted. I don't know how difficult it would be to implement.
I don't think it would be very difficult at all. Technically that is. Policy-wise it's a nightmare because you'd have to convince Debian to update the Debian Packaging Policy and update all the packages accordingly. But you kill two birds with one stone. You can run an application manager and a package manager of the same package database, and you can largely prevent orphaned dependencies (the only thorn in my eye with current package management systems).
Quoting:Well, I understand your point, but, just find it inane. That's what meta packages are for.... i.e. get the whole pig, or just a ham.
That's even more packages in the repository, making it more confusing for new users.
> Agreed, but I think what Dino is saying in that regard is that meta packages are severly under-utilized, and that most of the details presented to the end user should be in the form of easily understood meta packages.
Ah, is that what he meant! He started rambling on about the Bears, and my eyes glazed over ;-).
Yes, meta packages are a very useful & powerful tool. I think it's not so much that the metas aren't used, but rather that the descriptors are sometimes vague in the extreme. This is an area where improvement would benefit both experienced and new users.
Ah, is that what he meant! He started rambling on about the Bears, and my eyes glazed over ;-).
Yes, meta packages are a very useful & powerful tool. I think it's not so much that the metas aren't used, but rather that the descriptors are sometimes vague in the extreme. This is an area where improvement would benefit both experienced and new users.
I saw a bear once - at the zoo. My pa and his lady friend went backpacking up in the mountains (WV) and a bear or two came around the camp one night. I don't think his lady friend does much backpacking with him now. That said, I took a few classes in the Marines through City Colleges of Chicago (now Harold Washington College). All I ever did in Baltimore was eat and watch a pretty cool show. I guess I'll pull for the Bears.
I can certainly see why a list of packages can be confusing for some people. I think the Add/Remove Programs utility in Ubuntu is pretty cool. I wouldn't suggest replacing Synaptic, but using the Program manager would be really cool for a lot of people. What I like about it is that it usually doesn't include all the additional libraries and other files - all you see are programs geared for the desktop. If you want to install a DB server, or you're just a control freak (like me), then Synaptic is surely a better tool.
At least in that scenario, everyone - geek and non-geek - wins.
I can certainly see why a list of packages can be confusing for some people. I think the Add/Remove Programs utility in Ubuntu is pretty cool. I wouldn't suggest replacing Synaptic, but using the Program manager would be really cool for a lot of people. What I like about it is that it usually doesn't include all the additional libraries and other files - all you see are programs geared for the desktop. If you want to install a DB server, or you're just a control freak (like me), then Synaptic is surely a better tool.
At least in that scenario, everyone - geek and non-geek - wins.
Quoting: What you say about dependencies is absolutely correct, and something I have wanted. I don't know how difficult it would be to implement.This is already available in Debian when using aptitude (which works for both depends and recommends, but not for suggests). That is why i would choose aptitude over synaptic or any other package manager any day.
> That is why i would choose aptitude over synaptic
Huh???
I'd suggest you haven't used synatptic much lately. It does all that without the awkward aptitude interface.
Huh???
I'd suggest you haven't used synatptic much lately. It does all that without the awkward aptitude interface.
jimf,
I am unclear about that. If synaptic is based on apt-get then aptitude is a better choice imho because it has better dependency resolution than apt-get....
I am unclear about that. If synaptic is based on apt-get then aptitude is a better choice imho because it has better dependency resolution than apt-get....
> it has better dependency resolution than apt-get
Yeah, synaptic certainly does.... I won't say never, but, very, very rarely is there a conflict. Even then it's easy to resolve.
Yeah, synaptic certainly does.... I won't say never, but, very, very rarely is there a conflict. Even then it's easy to resolve.
Look guys, I might use aptitude if I had nothing else. It's certainly resolves dependencies better than apt, but I remember DOS apps that had a more intuitive interface. Synaptic would probably worth it just for the improved overview in the GUI interface, but....
* you can specify 'standard upgrade' (apt) or 'smart upgrade' (with dependency resolution) or 'ask'...
* You can list by 'pkg name', 'installed ver', 'latest ver', 'desc', and, a slew of other criteria.
* You can search by 'pkg name', 'name and description', 'ver', 'dependencies', 'provided packages', or, even 'maintainer'. You can also set up your own (combination) search criteria.
* Depending on your sources list, you can easily switch between, for example, testing and unstable; thus allowing you to maintain a mixed Distro with minimal risk.
* there is also page that categorizes apps by section, as well as settings for how you view, what you view, colors for app status, app and terminal behavior and text, etc, etc, etc.
If I've managed to establish a Desktop, why would I use something other than Synaptic?
* you can specify 'standard upgrade' (apt) or 'smart upgrade' (with dependency resolution) or 'ask'...
* You can list by 'pkg name', 'installed ver', 'latest ver', 'desc', and, a slew of other criteria.
* You can search by 'pkg name', 'name and description', 'ver', 'dependencies', 'provided packages', or, even 'maintainer'. You can also set up your own (combination) search criteria.
* Depending on your sources list, you can easily switch between, for example, testing and unstable; thus allowing you to maintain a mixed Distro with minimal risk.
* there is also page that categorizes apps by section, as well as settings for how you view, what you view, colors for app status, app and terminal behavior and text, etc, etc, etc.
If I've managed to establish a Desktop, why would I use something other than Synaptic?
Quoting:If I've managed to establish a Desktop, why would I use something other than Synaptic?
You're not an overwhelmed newbie.
Quoting:This is already available in Debian when using aptitude (which works for both depends and recommends, but not for suggests). That is why i would choose aptitude over synaptic or any other package manager any day.
There is one very big problem with Aptitude: It doesn't work on top of the APT database but alongside it. Things like unnecessary dependency removal only work if you installed all your applications through aptitude because it keeps it's own database of what has been installed where and why. That functionality needs to be pushed back into APT so it's available everywhere regardless of what package manager front-end you use. Someone should be able to install an application through the commandline and still be able to remove it (plus dependencies) through the GUI, whatever that GUI may be.
> You're not an overwhelmed newbie.
True enough, but if you use the simpler settings, and stay within the release settings you sure don't need to be an expert either. That gives people plenty of time to ramp up their skills.
Or are you saying that noobs shouldn't or just can't learn? ;-)
True enough, but if you use the simpler settings, and stay within the release settings you sure don't need to be an expert either. That gives people plenty of time to ramp up their skills.
Or are you saying that noobs shouldn't or just can't learn? ;-)
my 2 cents:
From the technical point of view, CNR has some unbeatable advantages: - Easy of luse, particularly for newly "converted" ex-wincrap lusers. - Ability to set up one centralised repository for several distros.
Obvious disatvantages: - Free client, non-free server. That means there's one central authority to rule them all. The usual trust issues, potential conflicts of interest, elevated "market entry barrier" and so on. All the stuff that made you ditch windows in the first place. - It's a third party repo effectively. Technical challenges for bug handling and maintenance of the repo, as well. Potential to be a big technical problem for non-Linspire distros. - .deb/.rpm/.tgz hell. One package fits all distros? not! Realistically, CNR package maintainers will have to provide dedicated packages for each distro or distro family. That will effectively eliminate the benefit of having one centralised repo.
The only benefit that's left is the ease of use. That is certainly worth going after, though. A free implementation of such a service already exists: klik http://klik.atekon.de/
Klik seems to be quite nice, indeed. However, there's still potential for technical difficulties as described above. In the end, it's up to each particular distro to embrace the idea or not.
From the technical point of view, CNR has some unbeatable advantages: - Easy of luse, particularly for newly "converted" ex-wincrap lusers. - Ability to set up one centralised repository for several distros.
Obvious disatvantages: - Free client, non-free server. That means there's one central authority to rule them all. The usual trust issues, potential conflicts of interest, elevated "market entry barrier" and so on. All the stuff that made you ditch windows in the first place. - It's a third party repo effectively. Technical challenges for bug handling and maintenance of the repo, as well. Potential to be a big technical problem for non-Linspire distros. - .deb/.rpm/.tgz hell. One package fits all distros? not! Realistically, CNR package maintainers will have to provide dedicated packages for each distro or distro family. That will effectively eliminate the benefit of having one centralised repo.
The only benefit that's left is the ease of use. That is certainly worth going after, though. A free implementation of such a service already exists: klik http://klik.atekon.de/
Klik seems to be quite nice, indeed. However, there's still potential for technical difficulties as described above. In the end, it's up to each particular distro to embrace the idea or not.
> In the end, it's up to each particular distro to embrace the idea or not.
True, but what that means is it's still unlikely there will be any 'universal' installer.
True, but what that means is it's still unlikely there will be any 'universal' installer.
Personally I don't like klik that much. I prefer my applications to be installed in the regular locations and not in some tucked away virtual filesystem. Nice for noobs but not for CLI people like me.
> True, but what that means is it's still unlikely there will be any 'universal' installer.
True, but there won't be one in the forseeable future, either way.
sander: While klik isn't perfect, the approach is quite ingenious in my opinion. One problem usually encountered with 3rd party repos or external packaging systems like openpkg is that they can introduced invasive changes to your systems, like overwriting files belonging to other packages etc. Putting all the files in a virtual file system image mitigates that risk.
Besides, klik and CNR are not designed for experienced people like you. You would just download a source tarball and "./configure - make - make install" it yourself. You might even make a .deb or .rpm out of the source tarball yourself. klik is designed to explicitly cater for those users who don't feel comfortable with CLI and all that packaging magic.
sander: While klik isn't perfect, the approach is quite ingenious in my opinion. One problem usually encountered with 3rd party repos or external packaging systems like openpkg is that they can introduced invasive changes to your systems, like overwriting files belonging to other packages etc. Putting all the files in a virtual file system image mitigates that risk.
Besides, klik and CNR are not designed for experienced people like you. You would just download a source tarball and "./configure - make - make install" it yourself. You might even make a .deb or .rpm out of the source tarball yourself. klik is designed to explicitly cater for those users who don't feel comfortable with CLI and all that packaging magic.
As far as 3rd party packagers go, klik is quite good yes. However, in what way is klik better than a distro's native packaging tool? The only thing I can think of is the package v.s. application thing I mentioned earlier in the thread. I don't think it has any added value on distro's that already provide an application manager (such as Ubuntu).
I'd probably do the latter. Stuff installed from tarballs tend to make my life a misery when it's time to upgrade. The only thing I actually install from tarballs are web applications because they can simply live entirely in a subdirectory below /var/www
Quoting:You would just download a source tarball and "./configure - make - make install" it yourself. You might even make a .deb or .rpm out of the source tarball yourself.
I'd probably do the latter. Stuff installed from tarballs tend to make my life a misery when it's time to upgrade. The only thing I actually install from tarballs are web applications because they can simply live entirely in a subdirectory below /var/www
Quoting:If I've managed to establish a Desktop, why would I use something other than Synaptic?I thought everyone knew that, obviously not. Good thing you highlighted the list for everyone. Besides, Synaptic is there, along with all the others on Debian based distros, so what the commotion is all about?
Quoting: I'd suggest you haven't used synatptic much lately. It does all that without the awkward aptitude interface.You mean synaptic now does automatic dependency removal, or showing only the packages that are not automatic dependencies, or showing the uninstalled recommended packages etc. If synaptic does all that then it would be much simpler to use that. As for the aptitude interface, it may be somewhat different to begin with but is a matter of getting used to.
Quoting: There is one very big problem with Aptitude: It doesn't work on top of the APT database but alongside it. Things like unnecessary dependency removal only work if you installed all your applications through aptitude because it keeps it's own database of what has been installed where and why. That functionality needs to be pushed back into APT so it's available everywhere regardless of what package manager front-end you use.This is a valid issue. In absence of this functionality in apt as of now, aptitude is the best choice imho particularly since the debian installer also uses it as the default PM.
"Besides, Synaptic is there, along with all the others on Debian based distros, so what the commotion is all about?"
We live in a world were clever marketing works better than developing good software, that's why there's so much commotion about a non-vital service like CNR.
Kevin Carmony: "Linux Linspire CNR jihad. CRN durka easy" Clueless IT journalists: "CNR durka durka durka"
We live in a world were clever marketing works better than developing good software, that's why there's so much commotion about a non-vital service like CNR.
Kevin Carmony: "Linux Linspire CNR jihad. CRN durka easy" Clueless IT journalists: "CNR durka durka durka"
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

Forgotten? I'm counting on it!