"cask" ports just keep on rolling in...

[Ken Cunningham]

What would we really need to do this properly?

The current fetch, checksum phases are OK.

The extract phase can be used as is for some software (simple copies), but for other software we don’t want to extract it, we want to run the installer.

The configure and build phases need to be overridden and disappear.

The destroot phase needs to — what — record the files that will be installed in some kind of an index file? And also know about the stuff that gets installed into ~/Library, etc.

Then run the “cask” destroot without installing any files into the actual destroot:

copy the apps and stuff
or 
run the installer
or
extract from the pkg
or 
… 

and then NOT have the entire software repackaged into a MP archive file to be stored 12 different times…

Or some such plan

Best,

Ken





> On Feb 5, 2021, at 11:00 AM, Ken Cunningham <ken.cunningham.webuse at gmail.com> wrote:
> 
> With no plan, we’ll just keep getting more and more of these.
> 
> <https://github.com/macports/macports-ports/pull/9936 <https://github.com/macports/macports-ports/pull/9936>>
> 
> This kind of port just repackages the DMG into many tgz archives.
> 
> It’s wasteful. People want them.
> 
> What we should have instead of this is some kinda tech that
> 
> 1. downloads the DMG
> 2. installs the app
> 3. records some way of uninstalling everything
> 
> 
> What we have instead is a repackaging of the DMG into many, identical, system-specific archive bundles.
> 
> Yuk.
> 
> Ken
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20210205/a316748e/attachment.htm>