You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
No
Describe you'd like
Yes, I understand that keka is an archiver, not a utility for working with disk images, but if there is an opportunity to expand the functionality of creating disk images, then it would be good.
DMG:
As I understood when creating a disk image from a folder .dmg, keka creates it with the HFS+ file system.
It would be convenient if it were possible to create a DMG with HFS+ and APFS file systems (and to have a choice between case-sensitive and case-independent).
P.S.
Perhaps someone will tell you why this functionality is needed in Keka, because with the help of a standard disk utility, you can create .dmg with APFS. Yes, this is true, but the disk utility has one disadvantage - it cannot create a DMG if the folder with files is not on APFS or HFS+ (but for example on exFAT) and then you have to move files to any partition with the native macOS file system. Keka creates DMG without any problems, even if the file folder is located on exFAT.
ISO:
As I understood when creating a disk image from a folder .dmg, keka creates it with the ISO9660 file system.
There has been a UDF file system for a long time and it would be convenient to have a choice between which file system it will be created with when creating an ISO disk image.
Thank you.
The text was updated successfully, but these errors were encountered:
Just to be clear APFS can't be used because is not possible in sandbox #159
It strange...
I wonder then how we achieved the possibility of choosing the APFS file system when creating a disk image in the DropDMG application https://c-command.com/dropdmg/
By the way, in the Dropdmg settings, you can make the dmg be uncompressed. If you have the time and opportunity, it would be convenient to have such functionality in Keka
By the way, in the Dropdmg settings, you can make the dmg be uncompressed. If you have the time and opportunity, it would be convenient to have such functionality in Keka
The uncompressed option is already available in that Keka build but called in a way no-one will know what it is 😅 It's the UDRO (R-O) aka read-only.
Probably I should add better explanations there.
I wonder then how we achieved the possibility of choosing the APFS file system when creating a disk image in the DropDMG application
DropDMG is not sandboxed, that's how it can perform that. I wish Apple hadn't implemented that restriction, even talked about that with the review team to no solution.
Is your feature request related to a problem? Please describe
No
Describe you'd like
Yes, I understand that keka is an archiver, not a utility for working with disk images, but if there is an opportunity to expand the functionality of creating disk images, then it would be good.
DMG:
As I understood when creating a disk image from a folder .dmg, keka creates it with the HFS+ file system.
It would be convenient if it were possible to create a DMG with HFS+ and APFS file systems (and to have a choice between case-sensitive and case-independent).
P.S.
Perhaps someone will tell you why this functionality is needed in Keka, because with the help of a standard disk utility, you can create .dmg with APFS. Yes, this is true, but the disk utility has one disadvantage - it cannot create a DMG if the folder with files is not on APFS or HFS+ (but for example on exFAT) and then you have to move files to any partition with the native macOS file system. Keka creates DMG without any problems, even if the file folder is located on exFAT.
ISO:
As I understood when creating a disk image from a folder .dmg, keka creates it with the ISO9660 file system.
There has been a UDF file system for a long time and it would be convenient to have a choice between which file system it will be created with when creating an ISO disk image.
Thank you.
The text was updated successfully, but these errors were encountered: