5 ms·

DMG (a disk image that can be mounted) is the main way to distribute OS X applications, and something this could have fulfilled the same use case if Linux wasn'

DMG (a disk image that can be mounted) is the main way to distribute OS X applications, and something this could have fulfilled the same use case if Linux wasn't as fond of centrally distributed packages.

icebraining 12y ago
It's not like Linux lacks disk image formats, though, like cloop (used by Knoppix). It's just that when you don't have to distribute weird metadata like resource forks, what's the point of using a whole filesystem versus a tar file?
- mikeash 12y ago
  Even when you do have weird metadata, it's easy enough to retrofit archive formats to handle it, which Mac OS X did years ago. Disk image distribution is a complete anachronism now, and it's odd how persistent it is.
  - lvillani 12y ago
    DMGs still have the advantage that you can customise the Finder windows that opens when you double click one [1]. So, from an UX standpoint, they still make a lot of sense to distribute application bundles since it compels users to "install" the application by dragging the bundle icon to the appropriate directory, which is conveniently symlinked in that Finder window. It's also easier to produce than a self-installing package. With a .zip or .tar.gz users would be left with an app bundle and no idea of where to put it. Generally they would just throw it somewhere random across the filesystem. At least, that's what non-technical Mac users I know happen to do. [1]: https://support.cdn.mozilla.net/media/uploads/gallery/images/2012-01-26-17-04-06-2b7732.png https://support.cdn.mozilla.net/media/uploads/gallery/images...
    - mikeash 12y ago
      I think the proper solution to that, if there's actually a problem with "somewhere random", is to have apps that move themselves on first launch. It's pretty easy to do, and IMO easier than creating a consistent build process for a good-looking dmg.
    - icebraining 12y ago
      The solution is to use a .tar file, but give it a custom extension (like, say, .deb) and so when the user double clicks on it, the system knows it's a software package and installs it in the appropriate directory.
    - Alupis 12y ago
      One can still install a program to "somewhere random across the filesystem" on most OS's, even Windows. It just so happens that by convention, most programs get installed to the "Program Files" directory, but that is not a requirement.
- xorcist 12y ago
  The only reason I can think of is DRM. Sometimes you are allowed to distribute physcial media, where keys are scrambled outside the regular filesystem, and perhaps there that allows for image distribution as well. But I'm guessing here.

icebraining 12y ago

It's not like Linux lacks disk image formats, though, like cloop (used by Knoppix). It's just that when you don't have to distribute weird metadata like resource forks, what's the point of using a whole filesystem versus a tar file?

mikeash 12y ago
Even when you do have weird metadata, it's easy enough to retrofit archive formats to handle it, which Mac OS X did years ago. Disk image distribution is a complete anachronism now, and it's odd how persistent it is.
- lvillani 12y ago
  DMGs still have the advantage that you can customise the Finder windows that opens when you double click one [1]. So, from an UX standpoint, they still make a lot of sense to distribute application bundles since it compels users to "install" the application by dragging the bundle icon to the appropriate directory, which is conveniently symlinked in that Finder window. It's also easier to produce than a self-installing package. With a .zip or .tar.gz users would be left with an app bundle and no idea of where to put it. Generally they would just throw it somewhere random across the filesystem. At least, that's what non-technical Mac users I know happen to do. [1]: https://support.cdn.mozilla.net/media/uploads/gallery/images/2012-01-26-17-04-06-2b7732.png https://support.cdn.mozilla.net/media/uploads/gallery/images...
  - mikeash 12y ago
    I think the proper solution to that, if there's actually a problem with "somewhere random", is to have apps that move themselves on first launch. It's pretty easy to do, and IMO easier than creating a consistent build process for a good-looking dmg.
  - icebraining 12y ago
    The solution is to use a .tar file, but give it a custom extension (like, say, .deb) and so when the user double clicks on it, the system knows it's a software package and installs it in the appropriate directory.
  - Alupis 12y ago
    One can still install a program to "somewhere random across the filesystem" on most OS's, even Windows. It just so happens that by convention, most programs get installed to the "Program Files" directory, but that is not a requirement.
xorcist 12y ago
The only reason I can think of is DRM. Sometimes you are allowed to distribute physcial media, where keys are scrambled outside the regular filesystem, and perhaps there that allows for image distribution as well. But I'm guessing here.