Opened 18 years ago
Closed 18 years ago
#10689 closed enhancement (fixed)
UPDATE: pwman-0.3.4
| Reported by: | mni@… | Owned by: | yeled@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.0 |
| Keywords: | Cc: | mni@…,markd@… | |
| Port: |
Description
pwman-0.3.4
the portfile can be found here: ATTACHED
Description: curses based password management program
Homepage: http://sourceforge.net/projects/pwman
Comments: only tested on intel
Attachments (4)
Change History (8)
Changed 18 years ago by mni@…
comment:1 Changed 18 years ago by markd@…
| Cc: | mni@… markd@… added |
|---|
port:package (using macports dependencies) is now the preferred way except when there are specific reasons not to. Is there a reason you want to use the older lib:libxxx:package specification?
comment:2 Changed 18 years ago by mni@…
I wanted to let PWman use the libxml2 supplied with MacOSX, instead of having it depend on compiling a new from MacPorts. The lib:-way searches the local system first, and only if not found, will it compile the MacPort version - just seemed like a very smart way to me :)
But if its preferered to keep dependencies inside MacPorts, I'll do that in the future.
Changed 18 years ago by mni@…
| Attachment: | Portfile.2.diff added |
|---|
Portfile patch using MacPorts dependencies
comment:3 Changed 18 years ago by mni@…
I have now added the new Portfile (and .diff) - containing only MacPorts dependencies.
comment:4 Changed 18 years ago by markd@…
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
It is prefered to use MacPorts dependencies for almost everything. There are exceptions like X11 and such and special cases for various reasons. But it makes for a much more predictible environment so it is preferred. Committed. Thanks!
Updated Portfile