Bug 144769 - [PATCH] ports-mgmt/portupgrade should have a configuration option to specify that some packages should alwayse be build from source even when using -P.
Summary: [PATCH] ports-mgmt/portupgrade should have a configuration option to specify ...
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: Chris Rees
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-15 19:10 UTC by Jeremy Pyne
Modified: 2012-04-16 18:33 UTC (History)
0 users

See Also:

Attachments
file.diff (2.55 KB, patch)
2010-03-15 19:10 UTC, Jeremy Pyne 		no flags Details | Diff
View All 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 Jeremy Pyne 2010-03-15 19:10:03 UTC 
The problem is that when using the portupgrade tool with the -P option to upgrade from packages when possible, there is no way to flag specific packages to still build from source.  You can hold packages from updating at all and then manually update them but this is not opportune.

Fix: This patch adds a USE_PORTS configuration option that you can set to flag specific ports to always update from source, if the have custom build options for example.  Any matching packages will not check for binary version on portupgrade -P but will just assume no package is available and build from source.  It makes for a much cleaner update process.

Patch attached with submission follows:
How-To-Repeat: 
Install a package from source (php5 and php5-mysql for example as they often need custom build options). 
Now do a package update with portupgrade -P.

The process will check for a binary package for this port witch we manually build and will overwrite it with the generic version if there was an update.  The only ways to prevent the losing or out custom version are to completely disable the updating of this package and its dependencies, thus requiring manual intervention for each case, or to do all portupgrades completely from source.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2010-03-18 04:31:15 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ruby

Fix synopsis and assign.
Comment 2 Philip M. Gollucci freebsd_committer freebsd_triage 2010-09-10 00:12:09 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:00 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:27 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:02 UTC 
State Changed
From-To: open->suspended

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

Over to maintainer.
Comment 7 Chris Rees freebsd_committer freebsd_triage 2012-04-12 11:03:22 UTC 
State Changed
From-To: suspended->open

This should not be suspended.
Comment 8 Bryan Drewery 2012-04-16 02:52:57 UTC 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This has been accepted and merged into the upstream. It is now available
in the latest portupgrade-devel port and will be included in the next
release.

Thanks,
Bryan Drewery
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPi3t4AAoJEG54KsA8mwz5ibsQAIx4ok+FDvzGegGcC0j0H8Wz
0yoJyk0pgT/cfACVMdscrW0P9K2tR17ab5YUbvHwU4tyxgGujb2eNSu7mKY994ye
1wa3MXj+9r4LURi5uoyVdIKtHx+/32RZyfVJeV9+GzS9h7/snrqEWZpqZokWCh0+
jSlpx+9VqCUeCDZiv3jfujhNcPc7YNo/L8iuGFtaNN+OC2m4DepKJD8auSYvwnZg
Ohu0hs6dCkBU33oOiDmdRzV+u1OLlV9Kx+xIR8n6zUwcfNGqVOdwKfHqSFLb6mNB
ojC1LIRc9PSEWCqX94yFjy+An3Gt8rZkdfDzjj4Bv/O5xMsUBhMEIbkKV4sb2Fhq
C5XFq32+8VflksKWiOu10NzwzSpUcAWjUDwtZlKuXg2DH4rjZXli2gmZ3t6O8Oz1
TdgvgtMWrjXvqntdQPouFe4X15NpDCWrwFK/IBHIImD3mluA50SpakgYbvGlQEmR
vdWiGMfYI8WZjMzn8uFdXsTyLRU8Ky+l1lTz+WOptr/cSBLy3fDsAPiGVgYJpY/a
bUyQnz2ngOb7hma3RNj/5vnftaecWQUbaE5aNlRkAg3dNCk6lDS8839qFzviOVOn
be96+c2RkPrhzzT8A1vaS67sj7A87FGrl0jchT+ob7YC/4FkQP960p+o4pQamfTf
dUYsCC+1F/aaJ3JVzuyU
=71oY
-----END PGP SIGNATURE-----
Comment 9 Chris Rees freebsd_committer freebsd_triage 2012-04-16 18:32:54 UTC 
State Changed
From-To: open->closed

Fixed in upstream.
Comment 10 Chris Rees freebsd_committer freebsd_triage 2012-04-16 18:33:16 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->crees

Take responsibility