Linked by Thom Holwerda on Wed 23rd Apr 2008 07:28 UTC
Ubuntu, Kubuntu, Xubuntu Tomorrow, Ubuntu's second 'long-term support' release, 8.04 or Hardy Heron, will propagate its way through the list of mirrors. OSNews took a short look at the beta release of Hardy Heron a few weeks ago, and concluded that "All in all, this release packs some interesting new features and frameworks, some of which should have been part of any Linux distribution three years ago. It is quite clearly a beta though, and definitely not ready yet to be labeled as a 'long term support' release." In anticipation of the release, El Reg caught up with Mark Shuttleworth in London.
Thread beginning with comment 310965
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Syncronizing releases
by J.R. on Wed 23rd Apr 2008 08:52 UTC in reply to "Syncronizing releases"
J.R.
Member since:
2007-07-25

Now, what about unifying package management too? Would the RPM distros be willing to drop YUM, URPMI, YAST and switch to deb/APT? Again, I'm afraid that's asking too much, but who knows, maybe some day... ;)


I am also very interested in seeing all the package management getting unified, but when even the same damn format is so dependent on the individual distro its no point. Like ubuntu debs being ubuntu specific and will not necessarily work on other distros that use debs...

I like the way Mac OS X has solved packet management though...

Reply Parent Bookmark Score: 5

RE[2]: Syncronizing releases
by segedunum on Wed 23rd Apr 2008 10:10 in reply to "RE: Syncronizing releases"
segedunum Member since:
2005-07-06

I like the way Mac OS X has solved packet management though...

Dumping everything into one folder is not the answer. When Apple has more people developing for the Mac, and there is more of a reliance on core, shared components, then they'll see why that is.

Reply Parent Bookmark Score: 6

RE[3]: Syncronizing releases
by J.R. on Wed 23rd Apr 2008 10:24 in reply to "RE[2]: Syncronizing releases"
J.R. Member since:
2007-07-25

"I like the way Mac OS X has solved packet management though...

Dumping everything into one folder is not the answer. When Apple has more people developing for the Mac, and there is more of a reliance on core, shared components, then they'll see why that is.
"

Well I see this perhaps from a different angle: if I want a packet that is NOT in the repository, how should this be installed? I don't want to have to add a new repository for each package I want to install (like seems to be the solution for ubuntu), and I don't want to be limited by what the repository maintainers says I should have access to. By downloading external packages these may or may not know what shared libraries (and versions) that are present on the target system (and here is the problem with different distros). Furthermore, spreading the files "all over the system" like many unixes does today is not very plesant when I want to remove or otherwise modify the stuff.

All I want is a system where I can download a single file from the vendors website and just click it and it works.

Reply Parent Bookmark Score: 4

RE[3]: Syncronizing releases
by sigzero on Wed 23rd Apr 2008 19:31 in reply to "RE[2]: Syncronizing releases"
sigzero Member since:
2006-01-03

Really? When does that scale tip? There are plenty of developers on Apple now.

I am also in the "really like Apple's way".

Reply Parent Bookmark Score: 2

RE[2]: Syncronizing releases
by Lennie on Wed 23rd Apr 2008 22:19 in reply to "RE: Syncronizing releases"
Lennie Member since:
2007-09-22

Maybe you didn't know this, but Mac uses deb underneath as well. :-)

So when you say, I don't like how the deb-distributions can be incompatible, but I like how the Mac handles it. You might not be making as much sense as you think you are.

As Mac is 'just' an other very-much-incompatible deb-based 'distribution'.

Update: fixed 2 typos, there might still exist other problems.

Edited 2008-04-23 22:32 UTC

Reply Parent Bookmark Score: 2