Bug 149817 - [wishlist] ports-mgmt/portupgrade: portinstall -p option doesn't make packages of build dependencies
Summary: [wishlist] ports-mgmt/portupgrade: portinstall -p option doesn't make package...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Bryan Drewery
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-19 23:00 UTC by Alvaro Martinez
Modified: 2012-08-26 16:40 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alvaro Martinez 2010-08-19 23:00:08 UTC 
when installing a port, usually one wishes to use the most of packages with -P option in portinstall, and if you like to use that port in several installations (like in a shared packages archive), its a good idea to use -p  also.
but if a port require differents dependencies for building than for installing, portinstall doesn't look for binary packages at installing those deps even if you specified -P. The same happens with -p, portinstall doesn't make packages of each build dependency. i think it sould

How-To-Repeat: everything like
portinstall -vRPp <port>
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2010-08-20 03:48:41 UTC 
Responsible Changed
From-To: freebsd-bugs->ruby

reclassify
Comment 2 Philip M. Gollucci freebsd_committer freebsd_triage 2010-09-10 00:12:27 UTC 
Responsible Changed
From-To: ruby->pgollucci

I will take it
Comment 3 Philip M. Gollucci freebsd_committer freebsd_triage 2010-09-24 07:23:59 UTC 
Responsible Changed
From-To: pgollucci->freebsd-ports-bugs

going to have enotime for the next 2 weeks, sorry
Comment 4 Steve Price freebsd_committer freebsd_triage 2011-01-03 17:25:49 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ruby

Over to maintainer(s).
Comment 5 Philip M. Gollucci freebsd_committer freebsd_triage 2012-02-22 05:24:13 UTC 
State Changed
From-To: open->suspended

Over to maintainer.
Comment 6 Philip M. Gollucci freebsd_committer freebsd_triage 2012-02-22 05:24:13 UTC 
Responsible Changed
From-To: ruby->freebsd-ports-bugs

Over to maintainer.
Comment 7 Bryan Drewery freebsd_committer freebsd_triage 2012-08-02 14:06:29 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->bdrewery

Over to maintainer.
Comment 8 Bryan Drewery freebsd_committer freebsd_triage 2012-08-26 16:31:11 UTC 
This is either now fixed, working correctly, or I am misunderstanding
something.

1. ports/143979 updated -PP (packages-only) to not install build deps as
the thought is if you only want packages, you'll never need the build deps.
2. Both -P and -PP save the fetched packages to /usr/ports/packages/All
by default.
3. Using -P, the build deps are properly fetched and saved.
4. Using -P on a port that I did not have a remote package for, but I
did have build dep packages for, it properly fetched packages for the
build deps, and then built the port that I did not have a package for.
It then saved the fetched packages.
5. Doing the same as 4, but including -p, properly built a package for
the port that was built as well as saved all fetched packages.

If I have misunderstood something, or there is still a feature you would
like to see added, please report to
https://github.com/pkgtools/pkgtools/issues

Regards,
Bryan Drewery
Comment 9 Bryan Drewery freebsd_committer freebsd_triage 2012-08-26 16:31:41 UTC 
State Changed
From-To: suspended->closed

Closing as not reproducible.