[MacPorts] #13848: esound library routine incorrectly identifies DISPLAY on Leopard (fwd)

2008-01-06 Thread robert delius royar
Because esound has no maintainer, I am copying this ticket to the developers' list. -- Forwarded message -- Date: Sun, 06 Jan 2008 13:57:41 - From: MacPorts [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Subject: [MacPorts] #13848:

Re: [32446] trunk/dports/sysutils/rpm-devel/Portfile

2008-01-06 Thread Markus Weissmann
On 5 Jan 2008, at 22:42, Ryan Schmidt wrote: On Jan 3, 2008, at 05:11, Anders F Björklund wrote: Ryan Schmidt wrote: Perhaps, but these -devel ports usally build from tip of trunk so they all had revision 0... Ports should never build from tip of trunk or HEAD or similar concepts.

Re: [32446] trunk/dports/sysutils/rpm-devel/Portfile

2008-01-06 Thread Landon Fuller
On Jan 5, 2008, at 1:42 PM, Ryan Schmidt wrote: On Jan 3, 2008, at 05:11, Anders F Björklund wrote: Ryan Schmidt wrote: Perhaps, but these -devel ports usally build from tip of trunk so they all had revision 0... Ports should never build from tip of trunk or HEAD or similar

Re: [32446] trunk/dports/sysutils/rpm-devel/Portfile

2008-01-06 Thread Anders F Björklund
Landon Fuller wrote: But that's not reproducible, and I thought we always wanted that. If I install a specific version of a port today, I should get the same software if I install that same version of that port tomorrow. By fetching from HEAD, you break that assumption. This is why I've

Re: [32446] trunk/dports/sysutils/rpm-devel/Portfile

2008-01-06 Thread Markus Weissmann
On 6 Jan 2008, at 21:20, Anders F Björklund wrote: Landon Fuller wrote: But that's not reproducible, and I thought we always wanted that. If I install a specific version of a port today, I should get the same software if I install that same version of that port tomorrow. By fetching from