On 2012-4-9 14:35 , Joshua Root wrote:
> On 2012-4-9 02:06 , Landon Fuller wrote:
>>
>> I think it should be noted that rev-upgrade isn't really optional
>> in the same way that 'upgrade outdated' is -- rev-upgrade is
>> detecting genuinely broken binaries and fixing them,
>> automatically.
>>
>> A
On Apr 8, 2012, at 8:18 PM, Ryan Schmidt wrote:
>
> Could these messages be presented using the "notes" feature instead of
> "ui_msg"?
I just followed what was established in the kde PortGroup for its similar
notification for DBUS. I have no objection to changing it, but it should be
done c
On 2012-4-9 14:22 , Ryan Schmidt wrote:
> I wanted to make sure this change made it in because I'm tired of dealing
> with the tickets.
If you need a break, then by all means take one.
> On Apr 8, 2012, at 22:40, Joshua Root wrote:
>
>> Applying restrictions to what distfiles may contain before
On 2012-4-9 02:06 , Landon Fuller wrote:
>
> I think it should be noted that rev-upgrade isn't really optional
> in the same way that 'upgrade outdated' is -- rev-upgrade is
> detecting genuinely broken binaries and fixing them,
> automatically.
>
> As an end user, I just want things to work. If
On 2012-4-8 18:28 , Ryan Schmidt wrote:
>
> We don't automatically upgrade a user's outdated ports; we make the user run
> "port outdated" and upgrade ports themselves on their own time, possibly by
> using "sudo port upgrade outdated". Why does rev-upgrade run automatically
> instead of making
On Apr 8, 2012, at 22:34, Joshua Root wrote:
> On 2012-4-8 21:42 , Ryan Schmidt wrote:
>>
>> I find it rude and upsetting that you reverted my change rather than
>> initiating a continuation of this thread yourself.
>
> I felt similarly about what appeared to be an attempt to sneak the
> change
On Apr 8, 2012, at 07:02, Arno Hautala wrote:
> I think the proxy issue is if there is an error on the user's end
> (misconfigured proxy, unacknowledged hotel wireless terms, etc.) this
> change could lead to port downloading from multiple sources and
> reporting that each is misbehaving. The corr
On 2012-4-8 22:02 , Arno Hautala wrote:
> I think the proxy issue is if there is an error on the user's end
> (misconfigured proxy, unacknowledged hotel wireless terms, etc.) this
> change could lead to port downloading from multiple sources and
> reporting that each is misbehaving. The correct fix
On 2012-4-8 21:42 , Ryan Schmidt wrote:
>
> I find it rude and upsetting that you reverted my change rather than
> initiating a continuation of this thread yourself.
I felt similarly about what appeared to be an attempt to sneak the
change into the release over my objections. Clearly we both
mis
On Apr 6, 2012, at 12:24, jerem...@macports.org wrote:
> Revision: 91597
> https://trac.macports.org/changeset/91597
> Author: jerem...@macports.org
> Date: 2012-04-06 10:24:08 -0700 (Fri, 06 Apr 2012)
> Log Message:
> ---
> xinit: Provide instructions for setting up the La
> kde4-1.1.tcl: don't hardcode /opt/local
hah! copy/pasta!
Thanks :-)
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
On Apr 8, 2012, at 18:22, take...@macports.org wrote:
> Revision: 91712
> https://trac.macports.org/changeset/91712
> Author: take...@macports.org
> Date: 2012-04-08 16:22:25 -0700 (Sun, 08 Apr 2012)
> Log Message:
> ---
> upc: revamped to 4.7.0.2
>
> Modified Paths:
> ---
On Apr 8, 2012, at 11:30, Jack Howarth wrote:
> question of why the Lion build bots are on such an old Xcode that they don't
> default all of the
> package builds to clang. Perhaps they should be updated to Xcode 4.3.2 and a
> bulk rebuild of the
> MacPorts package set started.
Please read:
h
On Apr 8, 2012, at 14:35, Jack Howarth wrote:
> Also non-sensical values like...
>
> sudo port -d install pymol +gcc49
>
> don't produce an error. Is that expected behavior for the error to be
> silently ignored by port?
Yes, that is expected.
___
> Also non-sensical values like...
>
> sudo port -d install pymol +gcc49
>
> don't produce an error. Is that expected behavior for the error to be
> silently ignored by port?
Variants are trickle down, so if a port doesn't have a variant it isn't
actually an error.
smime.p7s
Description: S/M
On Sun, Apr 08, 2012 at 12:48:14PM -0400, Jeremy Lavergne wrote:
> > The fact that, on Lion, MacPorts 2.0.4 installs perl/python that defaults
> > to llvm-gcc-4.2 made me
> > suspect that the binary packages installed on Lion were built with SL. If
> > not, this brings up the
> > question of why
On Sun, Apr 08, 2012 at 12:48:14PM -0400, Jeremy Lavergne wrote:
> > The fact that, on Lion, MacPorts 2.0.4 installs perl/python that defaults
> > to llvm-gcc-4.2 made me
> > suspect that the binary packages installed on Lion were built with SL. If
> > not, this brings up the
> > question of why
> The fact that, on Lion, MacPorts 2.0.4 installs perl/python that defaults to
> llvm-gcc-4.2 made me
> suspect that the binary packages installed on Lion were built with SL. If
> not, this brings up the
> question of why the Lion build bots are on such an old Xcode that they don't
> default all
On Sun, Apr 08, 2012 at 12:11:32PM -0400, Jeremy Lavergne wrote:
> > Perhaps MacPorts should consider separate binary repos for 10.4/10.5 and
> > 10.7/10.8. If all
> > of the binaries are built on Snow Leopard, this prevents those binary
> > MacPorts packages from
> > being built against the fort
> Perhaps MacPorts should consider separate binary repos for 10.4/10.5 and
> 10.7/10.8. If all
> of the binaries are built on Snow Leopard, this prevents those binary
> MacPorts packages from
> being built against the fortified 10.7 SDK and linked with -pie so that those
> executables won't
> le
On Sun, Apr 08, 2012 at 11:44:21AM -0400, Jeremy Lavergne wrote:
> > While this seems to work, we really need a setting in macports.conf to
> > allow the user to
> > disable binary downloads by defeult. Besides the issue of the wrong
> > compiler being used,
> > many folks would like to avoid the
On Apr 8, 2012, at 8:42 AM, Rainer Müller wrote:
> On 2012-04-08 13:57 , Clemens Lang wrote:
>> Not running rev-upgrade automatically will probably cause it never to be
>> run at all by the average user. We could run the analysis phase
>> automatically and instruct the user to issue port rev-upgr
> While this seems to work, we really need a setting in macports.conf to allow
> the user to
> disable binary downloads by defeult. Besides the issue of the wrong compiler
> being used,
> many folks would like to avoid the ancient llvm in llvm-gcc and use the most
> current
> llvm in the newest
On Sun, Apr 08, 2012 at 11:25:23AM -0400, Jeremy Lavergne wrote:
> > Why don't we have a flag to pass to port or a setting in
> > /opt/local/etc/macports to disable
> > binary downloads?
>
> You should be able to use -s for source only, and -b for binary only.
>
While this seems to work, we rea
> Why don't we have a flag to pass to port or a setting in
> /opt/local/etc/macports to disable
> binary downloads?
You should be able to use -s for source only, and -b for binary only.
smime.p7s
Description: S/MIME cryptographic signature
___
macpor
On Sun, Apr 08, 2012 at 11:14:42AM -0400, Jeremy Lavergne wrote:
> Ooops, forgot to reply to the list.
>
> > I also see the same breakage in MacPorts 2.0.4 when built from sources in
> > MacPorts-2.0.4.tar.bz2 using...
> >
> > ./configure && make && sudo make install
> >
> > under Xcode 4.3.2 on
Ooops, forgot to reply to the list.
> I also see the same breakage in MacPorts 2.0.4 when built from sources in
> MacPorts-2.0.4.tar.bz2 using...
>
> ./configure && make && sudo make install
>
> under Xcode 4.3.2 on Lion. When executing 'sudo port -v selfupdate', port is
> blindly
> using llvm-
On Sun, Apr 08, 2012 at 10:18:30AM -0400, Jack Howarth wrote:
>It appears that the new MacPorts 2.0.4 release when clean installed from
> the Lion dmg breaks the usage of clang as the default compiler for package
> building
> under Xcode 4.3.2. If you execute 'sudo port -d install pymol', you
It appears that the new MacPorts 2.0.4 release when clean installed from
the Lion dmg breaks the usage of clang as the default compiler for package
building
under Xcode 4.3.2. If you execute 'sudo port -d install pymol', you will observe
that /usr/bin/llvm-gcc-4.2 is used when building all the
On 2012-04-08 13:57 , Clemens Lang wrote:
> Not running rev-upgrade automatically will probably cause it never to be
> run at all by the average user. We could run the analysis phase
> automatically and instruct the user to issue port rev-upgrade to trigger
> the rebuild manually when problems occu
On Sun, Apr 8, 2012 at 07:57, Clemens Lang wrote:
> On Sun, Apr 08, 2012 at 03:28:47AM -0500, Ryan Schmidt wrote:
>
>> It's unclear what I'm meant to do with the warnings about files not
>> existing.
>
> Those are the reasons rev-upgrade will attempt to rebuild ports. We
> could omit them from the
On Sun, Apr 8, 2012 at 07:42, Ryan Schmidt wrote:
>
> Let's discuss it now. (Or, tomorrow; I need to sleep.) I want this change in
> MacPorts 2.1.0. Please help me understand what your objections are.
>
> [...]
>
> and raised a second concern about proxy servers, which I did not understand
If I
On 2012-4-8 21:42 , Ryan Schmidt wrote:
>
> You added in the ticket that you still disagree with this for all the reasons
> originally stated in the original ticket two years ago -- reasons you did not
> raise again in this thread in January. You asked one question which I
> answered, and raise
On Sun, Apr 08, 2012 at 03:28:47AM -0500, Ryan Schmidt wrote:
> > Should be fixed.
Thanks, Jeremy.
> > ---> Updating database of binaries: 53.5%
> > Warning: Error determining file type of
> > `/Volumes/work/macports/lib/ocaml/site-lib/stublibs/.turd_ocaml-findlib':
> > lstat(/Volumes/work/mac
On Jan 11, 2012, at 12:26, Ryan Schmidt wrote:
> On Jan 3, 2012, at 10:37, Joshua Root wrote:
>
>> On 2012-1-4 03:34 , Jeremy Lavergne wrote:
How are you planning to tell which checksum mismatches are from bad DNS
lookups and which are from a stealth update or broken proxy? Downloading
Moving this discussion to macports-dev.
On 8 apr 2012, at 13:16, Ryan Schmidt wrote:
> On Apr 8, 2012, at 06:12, Daniel Ericsson wrote:
>
>> I'd make a distinction between ports that only supply an end user binary and
>> those that supply a library that can be developed against. Doesn't feel
>
On Apr 6, 2012, at 14:05, macsforever2...@macports.org wrote:
> Revision: 91602
> https://trac.macports.org/changeset/91602
> Author: macsforever2...@macports.org
> Date: 2012-04-06 12:05:58 -0700 (Fri, 06 Apr 2012)
> Log Message:
> ---
> fasthenry-wr: Drop to llvm-gcc if u
On Apr 8, 2012, at 02:10, Joshua Root wrote:
> It's just rev-upgrade failing to run. The actual error causing it to
> fail is not "Error determining file type" etc. BTW, it's:
>
> invalid command name ""
>while executing
> "[registry::entry owner [$f path]] name"
>
> i.e. [registry::entry o
On Apr 6, 2012, at 15:50, jerem...@macports.org wrote:
> Revision: 91604
> https://trac.macports.org/changeset/91604
> Author: jerem...@macports.org
> Date: 2012-04-06 13:50:47 -0700 (Fri, 06 Apr 2012)
> Log Message:
> ---
> pari: Don't build ppc on intel
>
> Modified Path
On 2012-4-8 15:12 , Ryan Schmidt wrote:
>
> On Apr 7, 2012, at 20:16, Ryan Schmidt wrote:
>
>> ---> Updating database of binaries: 3.8%
>> Warning: Error determining file type of `/opt/local/bin/prove':
>> lstat(/opt/local/bin/prove):no such file or directory
>> Error: Updating database of bina
40 matches
Mail list logo
