modify install/package targets to depend on a new destroot target

[robert@…]

Original post: I have been using DarwinPorts for a little while now, and I'd like to pose a question/suggestion:

I have noticed that you can install packages using "port install" which builds them in "destroot" and then copies the data to "prefix" and makes the appropriate registry (receipt) file. I also noticed that if you do a "port package" it does the "port install" and then makes the package (presumably from the "destroot" data.

What I'm wondering is, maybe the "port package" command should do a "half install" (e.g. run the install into "destroot", but not copy the data to "prefix") and then build the package file. Then, make the "port install" command install the package file using the Apple installer. This would allow all the packages to be tracked by the installer system.

On the flip side, if you didn't run "port package" (no .pkg file has been created under "work"), the "port install" would just do the install and copy from "destroot" to "prefix" like it usually does.

This would allow either method of tracking the packages installed based on user preference.

-Robert

Possible solution: This is an excellent idea. But I think in order for this to be implemented, we should create a portdestroot.tcl (and "port destroot foo") target. "port install" would depend on this stage being completed, as well as "port package" (and "port rpmpackage").

If you have some time to look at this and implement it, I think we'd be more than happy to merge it in.

The only issue is convert the several ports that use post-install actions to be post-destroot actions. This will probably be a somewhat manual process. We would need to do both together.

Shantonu

[robert@…]

This has been completed and committed by Jordan Hubbard. I've reassigned this to him to close since he did all the work. :)

Thanks Jordan!!!!