Ticket #14887 (tesseract)

[Mark Anderson]

I posted a ticket with a Portfile for the tesseract OCR engine, can  
someone please commit it?


Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Error building octave from port

[Mark Anderson]

I had this very same problem, check out this ticket:
http://trac.macports.org/projects/macports/ticket/13686

I managed to get Octave 3.0.0 to build using the Portfile in this  
ticket.


—Mark

On Apr 4, 2008, at 1:24 PM, Jean-François Gobin wrote:


Hi,

I'm trying to install octave. It chokes :

make -C ../../scripts DOCSTRINGS
make[4]: `DOCSTRINGS' is up to date.
making arith.texi from arith.txi
/bin/sh: line 1:  2592 Segmentation fault  ./munge-texi -d ../../ 
src/DOCSTRINGS -d ../../scripts/DOCSTRINGS  arith.txi  arith.texi-t

make[3]: *** [arith.texi] Error 139
make[2]: *** [interpreter] Error 2
make[1]: *** [doc] Error 2
make: *** [all] Error 2

Error: Status 1 encountered during processing.

Version is octave-2.9.15

Going a bit deeper into what happens :

jfg:interpreter jean-francoisgobin$ gdb munge-texi
GNU gdb 6.3.50-20050815 (Apple version gdb-768) (Tue Oct  2 04:07:49  
UTC 2007)

Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and  
you are
welcome to change it and/or distribute copies of it under certain  
conditions.

Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for  
details.
This GDB was configured as i386-apple-darwin...Reading symbols for  
shared libraries  done


(gdb) run -d ../../src/DOCSTRINGS -d ../../scripts/DOCSTRINGS   
arith.txi  arith.texi-t
Starting program: /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_math_octave/work/octave-2.9.15/doc/ 
interpreter/munge-texi -d ../../src/DOCSTRINGS -d ../../scripts/ 
DOCSTRINGS  arith.txi  arith.texi-t

Reading symbols for shared libraries +++. done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: 13 at address: 0x
0x8fe18b42 in __dyld_misaligned_stack_error ()

Seems someone is trying to play with a null pointer

jF



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Using mplayer through Finder

[Mark Anderson]

Try using RCDefaultApp: http://www.rubicode.com/Software/RCDefaultApp/

Mark

On Sun, May 31, 2009 at 11:26 AM, Kal kalou...@gmail.com wrote:

 Nobody knows ? :-/

 There should be a trick, like building a .app file si it can be associated
 to video files in Finder...


 On Sat, May 30, 2009 at 9:12 PM, Kal kalou...@gmail.com wrote:

 Hi,

 I've installed mplayer-svn with MacPorts. However, I can use mplayer only
 through terminal. I can't launch a movie with mplayer when i'm using Finder.
 It's impossible to associate mplayer to an AVI file. Is there a trick to get
 video files associeted with mplyer binary file ?

 Cheers
 --
 Kal




 --
 Kal

 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: View/Hide /opt folder from Finder

[Mark Anderson]

If you've Setfile -a V, you can Cmd-Shift-Period from the Open/Save
Dialog, and it will show hidden files.  (10.6 only)

Mark

On Fri, Nov 6, 2009 at 1:53 PM, Steven Rogers sroge...@gmail.com wrote:

 On Nov 6, 2009, at 6:15 AM, Luís Beça wrote:

 How can I View/Hide the /opt folder from Finder? I have a laptop with
 macports installed
 that for some reason does not display the /opt folder in the Finder...

 You can temporarily get around it by just going to Finder = Go = Go to
 folder . . .   and typing in /opt  - that will give you a finder window.
 There are ways to change the defaults for what is hidden and what isn't. If
 you want to change visibility permanently - give it a google. I think there
 are some apps which provide an easy interface for it. I just use
 shift-command-G which usually has /opt/local or ~/.ssh already in it . . .

 SR


 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: qt4-mac update fails to compile

[Mark Anderson]

I got this one too.  I had to manually change all of those -arch
-Xarch_x86_64 to -arch x86_64 -Xarch_x86_64, and by manually, I mean
with Perl. Then it compiled just fine.  I was thinking of filing a
ticket, but I'm not sure how to fix it from our end.  I think it's a
QT4 problem, and I can't find exactly what needs to be patched.

Mark

On Sat, Jan 9, 2010 at 7:32 AM, David Evans dave.evan...@googlemail.com wrote:
 Chris Jones wrote:
 Hi,

 OS X 10.6 intel. Attempting to upgrade qt4-mac gives the error below. Does 
 anyone else see this ?



 I have had problems with qt4-mac compiling with ccache enabled in the past.
 See ticket 18912.  Please try again with ccache disabled.

 I also get an error with qt4-mac, but it's not the same as yours.

 :info:build /usr/bin/g++-4.2 -arch x86_64 -Xarch_x86_64 \
  -mmacosx-version-min=10.5 -arch -Xarch_x86_64 \
   -mmacosx-version-min=10.5 -o ../../../bin/moc \
  release-shared/moc.o release-shared/preprocessor.o \
  release-shared/generator.o release-shared/parser.o \
  release-shared/token.o release-shared/main.o  \
  -L/opt/local/lib -L/opt/local/var/macports/build/\
 _Users_davidevans_macports_svn-repo_macports-trunk_dports_aqua_qt4-mac/\
  work/qt-everywhere-opensource-src-4.6.0/src/tools/bootstrap \
 -lbootstrap -L/opt/local/lib -lz -framework CoreServices
 :info:build g++-4.2: Invalid arch name : -Xarch_x86_64
 :info:build make[1]: *** [../../../bin/moc] Error 1
 :info:build make: *** [sub-moc-make_default-ordered] Error 2

 I'll wait a few days to see if anyone has the same error before filing a
 tcket.

 OS X 10.6.2
 Xcode 3.2.1

 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Building time for qt4-mac

[Mark Anderson]

I would also maybe try port -v install qt4-mac or whatever, then you
can see the build process to see if it's really stalled.   Ryan is
right though, qt4-mac is a monster build, and takes forever.  I think
it took almost an hour on my 8 core mac pro.

Mark

On Mon, Mar 15, 2010 at 7:40 AM, Ryan Schmidt ryandes...@macports.org wrote:
 On Mar 15, 2010, at 05:41, macports-users-ow...@lists.macosforge.org wrote:

 From: Carsten Bessing cars...@bessing.net
 Date: March 15, 2010 05:41:02 CDT
 To: macports-users@lists.macosforge.org
 Subject: Building time for qt4-mac


 Hi,

 I'm trying to install digikam via MacPorts, but the process seems to stall 
 while 'building qt4-mac' - unless this building alone is supposed to take 
 over an hour.

 I'm on a MacBook Pro, 2.16 GHz Intel Core 2 Duo with 3 GB RAM, OS X 10.6.2.

 After well over an hour I interrupted the process and retried with the debug 
 flag. I have attached the output, if anyone has the time to tell me if I'm 
 just being impatient - or something is wrong.

 I'm new to this whole MacPorts thing, so any help would be most appreciated.

 Thanks,

 Carsten
 QT4.pdf

 Your original post did not make it to the mailing list because it was 1MB in 
 size, which is much too large to send to a group with this many subscribers.

 You should simply retry the build. (It will continue where it left off, 
 unless you cleaned it.) qt4-mac does take a very very very long time to build 
 (hours on my similar MacBook Pro), and if I recall, about 6GB of disk space. 
 You'll just have to be patient.


 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: ffmpeg doesn't build with leopard

[Mark Anderson]

I added this to my portfile, seemed to do the trick. Seems that
assembly and OSX still don't get along.

configure.args-append --disable-mmx

Mark

On 10/27/07, Michael Staggs [EMAIL PROTECTED] wrote:
 I used the following command line:   sudo port -v install ffmpeg +a52
 +faac +faad +gpl +lame +x264 +xvid

 And I get this:

 make -C libavcodec  all
 gcc -dynamiclib -Wl,-single_module -Wl,-install_name,/opt/local/lib/
 libavcodec.dylib,-current_version,51.1.0,-compatibility_version,51.1.0
 -Wl,-read_only_relocs,suppress -Wl,-dynamic,-search_paths_first -L/opt/
 local/lib -o libavcodec.51.dylib bitstream.o utils.o allcodecs.o
 mpegvideo.o jrevdct.o jfdctfst.o jfdctint.o resample.o resample2.o
 dsputil.o motion_est.o imgconvert.o mpeg12.o simple_idct.o
 ratecontrol.o eval.o error_resilience.o raw.o faandct.o parser.o
 h264idct.o rangecoder.o h263.o opt.o bitstream_filter.o audioconvert.o
 imgresample.o i386/fdct_mmx.o i386/cputest.o i386/dsputil_mmx.o i386/
 mpegvideo_mmx.o i386/motion_est_mmx.o i386/simple_idct_mmx.o i386/
 idct_mmx_xvid.o i386/fft_sse.o i386/fft_3dn.o i386/fft_3dn2.o aasc.o
 ac3enc.o ac3tab.o ac3.o alac.o asv1.o atrac3.o mdct.o fft.o avs.o
 bethsoftvideo.o bmp.o bmpenc.o c93.o cavs.o cavsdsp.o golomb.o
 cinepak.o cljr.o cook.o cscd.o cyuv.o dca.o dnxhddec.o dsicinav.o
 dvbsubdec.o dvbsub.o dvdsubdec.o dvdsubenc.o dv.o dxa.o 8bps.o ffv1.o
 huffyuv.o flac.o flacenc.o flashsv.o flashsvenc.o flicvideo.o 4xm.o
 fraps.o gifdec.o lzw.o gif.o h261dec.o h261.o h261enc.o h263dec.o
 h264.o cabac.o idcinvideo.o imc.o indeo2.o indeo3.o interplayvideo.o
 dpcm.o jpeglsdec.o jpegls.o mjpegdec.o mjpeg.o jpeglsenc.o kmvc.o
 ljpegenc.o mjpegenc.o loco.o mace.o mjpegbdec.o mmvideo.o
 mpegaudiodec.o mpegaudiodecheader.o mpegaudio.o mpegaudiodata.o
 mpegaudioenc.o mpc.o msmpeg4.o msmpeg4data.o msrle.o msvideo1.o lcl.o
 nuv.o rtjpeg.o pnmenc.o pnm.o png.o ptx.o qdm2.o qdrw.o qpeg.o qtrle.o
 ra144.o ra288.o roqvideo.o roqaudioenc.o rpza.o rv10.o sgidec.o
 sgienc.o rle.o shorten.o smacker.o smc.o snow.o sonic.o sp5xdec.o
 svq1.o targa.o targaenc.o vp3.o xiph.o vp3dsp.o tiertexseqv.o tiff.o
 tiffenc.o lzwenc.o truemotion1.o truemotion2.o truespeech.o tscc.o
 tta.o txd.o s3tc.o ulti.o vc1.o vc1data.o vc1dsp.o vcr1.o vmdav.o
 vmnc.o vorbis_dec.o vorbis.o vorbis_data.o vorbis_enc.o vp5.o vp56.o
 vp56data.o vp6.o vqavideo.o wavpack.o wmadec.o wma.o wmaenc.o wnv1.o
 ws-snd1.o xan.o xl.o zmbv.o zmbvenc.o pcm.o adpcm.o adx.o g726.o
 a52dec.o faac.o faad.o mp3lameaudio.o x264.o xvidff.o xvid_rc.o
 aac_parser.o aac_ac3_parser.o ac3_parser.o cavs_parser.o dca_parser.o
 dvbsub_parser.o dvdsub_parser.o h261_parser.o h263_parser.o
 h264_parser.o mjpeg_parser.o mpeg4video_parser.o mpegaudio_parser.o
 mpegvideo_parser.o pnm_parser.o vc1_parser.o dump_extradata_bsf.o
 remove_extradata_bsf.o noise_bsf.o mp3_header_compress_bsf.o
 mp3_header_decompress_bsf.o mjpega_dump_header_bsf.o
 imx_dump_header_bsf.o pthread.o i386/idct_mmx.o i386/cavsdsp_mmx.o
 i386/snowdsp_mmx.o i386/vp3dsp_mmx.o i386/vp3dsp_sse2.o -L/opt/local/
 var/macports/build/
 _opt_local_var_macports_sources_rsync
 .macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavutil -
 lavutil -lz -la52 -lmp3lame -lm -lxvidcore -lx264 -lfaac -lfaad
 ld: warning codegen in _sad8_xy2_mmx2 (offset 0x001B) prevents
 image from loading in dyld shared cache
 ld: warning codegen in _sad16_xy2_mmx2 (offset 0x002C) prevents
 image from loading in dyld shared cache
 ld: warning codegen in _sad16_xy2_mmx2 (offset 0x0084) prevents
 image from loading in dyld shared cache
 ld: absolute addressing (perhaps -mdynamic-no-pic) used in
 _avg_qpel8_mc20_mmx2 from i386/dsputil_mmx.o not allowed in slidable
 image
 collect2: ld returned 1 exit status
 make[1]: *** [libavcodec.51.dylib] Error 1
 make: *** [lib] Error 2

 Warning: the following items did not execute (for ffmpeg):
 org.macports.activate org.macports.build org.macports.destroot
 org.macports.install
 Error: Status 1 encountered during processing.

 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: Mac::Growl?

[Mark Anderson]

I can give it a look on Sunday.  I'm planning to use cpan2port, so you
may want to give that a try that yourself, might (I stress might) be
easy.

Mark

On Fri, Apr 30, 2010 at 10:57 PM, Steve Morris st...@judgement.com wrote:
 Is it possible to get the CPAN package Mac::Growl ported?

 Thanks
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Error building teTeX

[Mark Anderson]

Total aside, you should probably try texlive, as it is maintained.

Mark

On Mon, May 10, 2010 at 2:42 AM, Ryan Schmidt ryandes...@macports.org wrote:

 On May 10, 2010, at 01:28, Vincent DIEMUNSCH wrote:

 I try to install teTeX on my MacBookPro (OS 10.6.3) and I get the following 
 error (see below).

 i686-apple-darwin10-gcc-4.2.1: 1/lib: No such file or directory

 See:

 http://trac.macports.org/wiki/ProblemHotlist#lib-spaces

 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Orpie

[Mark Anderson]

Can you try again with port -v, and post the error messages?

—Mark

On Tue, Oct 19, 2010 at 3:51 PM, Vincent DIEMUNSCH 
vincent.diemun...@gmail.com wrote:

 Hello,

 I have tried to install Orpie many times, but i get the following :

  install orpie
 ---  Computing dependencies for orpie
 ---  Fetching orpie
 ---  Attempting to fetch orpie-1.5.1.tar.gz from
 http://lil.fr.distfiles.macports.org/orpie
 ---  Verifying checksum(s) for orpie
 ---  Extracting orpie
 ---  Configuring orpie
 ---  Building orpie
 Error: Target org.macports.build returned: shell command failed
 Log for orpie is at:
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_orpie/main.log
 Error: Status 1 encountered during processing.
 To report a bug, see http://guide.macports.org/#project.tickets

 I am under OS X 10.6.

 Can you help me ?

 Thanks.

 Vincent
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Orpie

[Mark Anderson]

/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_orpie/work/orpie-1.5.1
  /usr/bin/make all  returned error 2
 Error: Target org.macports.build returned: shell command failed
 Warning: the following items did not execute (for orpie):
 org.macports.activate org.macports.build org.macports.destroot
 org.macports.install
 Log for orpie is at:
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_orpie/main.log
 Error: Status 1 encountered during processing.
 To report a bug, see http://guide.macports.org/#project.tickets


 Le 19 oct. 2010 à 21:55, Mark Anderson a écrit :

 Can you try again with port -v, and post the error messages?

 —Mark

 On Tue, Oct 19, 2010 at 3:51 PM, Vincent DIEMUNSCH 
 vincent.diemun...@gmail.com wrote:

 Hello,

 I have tried to install Orpie many times, but i get the following :

  install orpie
 ---  Computing dependencies for orpie
 ---  Fetching orpie
 ---  Attempting to fetch orpie-1.5.1.tar.gz from
 http://lil.fr.distfiles.macports.org/orpie
 ---  Verifying checksum(s) for orpie
 ---  Extracting orpie
 ---  Configuring orpie
 ---  Building orpie
 Error: Target org.macports.build returned: shell command failed
 Log for orpie is at:
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_orpie/main.log
 Error: Status 1 encountered during processing.
 To report a bug, see http://guide.macports.org/#project.tickets

 I am under OS X 10.6.

 Can you help me ?

 Thanks.

 Vincent
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: MacTex vs MacPorts

[Mark Anderson]

I've been meaning to make a BibDesk port for a while now. I don't recognize
the others. Otherwise, MacPorts is pretty up to date. Especially if you
install texlive+full

Mark

On Sat, Oct 1, 2011 at 12:54 AM, Scott Webster sewebs...@gmail.com wrote:

 On Fri, Sep 30, 2011 at 9:34 PM, Richard L. Hamilton rlha...@smart.net
 wrote:
  I imagine that if all the components were in MacPorts, it would be easy
 enough to have a meta-port that just existed to give single name to cause
 all the rest to be installed.
 

 Probably if you install texlive+full you get a lot of stuff :)  I
 didn't test this in my particular case.  Perhaps it would have solved
 my issues.

 Scott
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: How can I control the Perl version I want?

[Mark Anderson]

Install perl5 +perl_514 instead of perl5 +perl5_12

I think that should work.

Mark

On Thu, Jan 5, 2012 at 1:24 PM, Rodolfo Aramayo raram...@gmail.com wrote:

 perl5 @5.12.3_1+perl5_12
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: UsingTheRightCompiler

[Mark Anderson]

Clang also compiles way faster for me, and the binaries are faster. I'd
like to keep GCC only to where clang breaks.

Mark

On Mon, Apr 16, 2012 at 11:51 AM, Jeff Singleton gvib...@gmail.com wrote:

 If you had read my entire email you would have seen that I have tried
 building (rebuilding) everything again.

 I guess the reason I am asking for what I am … is that (for example), the
 less popular HomeBrew for OS X offers methods for using GCC (a switch for
 'install --use-gcc') as my preferred compiler, and not defaulting to
 Apple's default compiler. I just was hoping that the maintainers for the
 overall MP sources would create something similar.

 If you are able to build Pango weekly…then you must be doing something
 differently that I.  Possibly not using the same Arch/Platform or possibly
 you customize your Portfile prior to building.  My issues stem from the
 default Portfile and using MacPorts pretty much as is, with some minor
 variant changes and setting x86_64 only as my build_arch. (Though I have
 tried i386 and get the same results).

 Jeff

 On Mon, Apr 16, 2012 at 5:33 AM, Jeremy Lavergne 
 jer...@lavergne.gotdns.org wrote:

  There simply HAS to be some way of forcing Macports to use the compiler
 that I want to use and not argue and not make changes whenever and just do
 what I tell it to.

 There is a default compiler option in trunk, but no one is having the
 issues you are (I build pango weekly to make installers for PSPP).
 Have you tried rebuilding all your packages?



 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: homebrew and macports together?

[Mark Anderson]

:) Not much, if any. But the reverse is constantly true. LaTeX is the one
that got me to convert people in the CS department.

—Mark
___
Mark E. Anderson e...@emer.net


On Fri, Aug 9, 2013 at 7:08 AM, Chris Jones jon...@hep.phy.cam.ac.ukwrote:


  Create a homebrew port of awesome.

 That way, not only will you get what you wanted,
 but everyone will benefit from the fruits of your labor.


  ... or take the more enlightened route and switch to using exclusively
 MacPorts ;) Is there anything Homebrew has than MP doesn't ?


 __**_
 macports-users mailing list
 macports-users@lists.**macosforge.orgmacports-users@lists.macosforge.org
 https://lists.macosforge.org/**mailman/listinfo/macports-**usershttps://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Port won't install on 10.9

[Mark Anderson]

You need to install from svn trunk. Or at least that has been the best
experience I have had.

—Mark
___
Mark E. Anderson e...@emer.net


On Sun, Oct 13, 2013 at 1:29 AM, PJW pengjingwen1...@gmail.com wrote:

 I try to install using source file (MacPorts-2.2.0.tar.gz) and failed.
 There’s no pkg package for Mac OS X 10.9.
 How did you install the binary distribution.

 
 PengJingwen
 Major in Everything.
 

 On Oct 13, 2013, at 1:18 PM, Brian D. McGrew br...@visionpro.com wrote:

  Are you trying to install port from binary distribution or source???
  Although it's not supported, I installed the binary distribution in
 Mavericks and built and installed gcc-4.8.1 universal just fine.
 
  -brian
 
  Sent from my iPhone
 
  On Oct 12, 2013, at 22:15, PJW pengjingwen1...@gmail.com wrote:
 
  Yes, I have installed Xcode 5 and Command Line Tools.
 
  I download the Mavericks GM DMG image , format my MacBook and install
 the new version of Mac. Everything is OK except MacPorts.
 
  Waiting for the New MacPorts.
  
  PengJingwen
  Major in Everything.
  
 
  On Oct 13, 2013, at 1:08 PM, Ryan Schmidt ryandes...@macports.org
 wrote:
 
  On Oct 12, 2013, at 20:23, PJW pengjingwen1...@gmail.com wrote:
 
  Who can tell me how to install MacPorts ins Mac OS X 10.9 GM.
  Thanks a lot.
 
  I got a error when configure.
  configure: error: Can't find Tcl configuration definitions
 
 
  Did you install Xcode *and* its command line tools?
 
  Mavericks is not yet released and is not yet supported by MacPorts.
 
  ___
  macports-users mailing list
  macports-users@lists.macosforge.org
  https://lists.macosforge.org/mailman/listinfo/macports-users

 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: changing default perl

[Mark Anderson]

I've added a patch. I had one when I did perl 5.18 which i meant to add to
the ticket, but forgot. Although we do need to come up with a better perl
strategy. The current workings drive me crazy.

—Mark
___
Mark E. Anderson e...@emer.net


On Sun, Nov 3, 2013 at 4:31 PM, Ryan Schmidt ryandes...@macports.orgwrote:


 On Nov 3, 2013, at 15:06, Puneet Kishor wrote:

  So, could one of kind and gentle folks tell in non-technical language
 the incantation to make p5.18 default?

 I suggest you wait until a perl5_18 variant is added to the perl5 port:

 https://trac.macports.org/ticket/41160

 Then, use that (using the commands you tried before).


 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: changing default perl

[Mark Anderson]

I'm all for doing what we need to do. I use a lot of perl, and I have
always tried to install the latest or close to latest. Back before we had
the perl5 port I had a perl script that read every port file and
essentially did this: s/perl5.8/perl5.12/ - so I'm a big fan of having the
latest available.

I'm also willing to help with whatever we need to fix. Sometimes, I think
I'm the last Perl fan around, as everyone ditches me for Python, which to
be fair, I also use.

—Mark
___
Mark E. Anderson e...@emer.net


On Sun, Nov 3, 2013 at 5:00 PM, Jeremy Lavergne
jer...@lavergne.gotdns.orgwrote:

  I’m not sure that making more work is really something we want to do.
 
  Right. But I’m not sure what course of action you’re advocating with
 that sentence.

 Introducing another perl5 variant means that’s another set of ports and
 their variants we need to clean up if we were to switch to perl_select. We
 would end up undoing anything new we add for perl variants.

 It would be less wasted effort to start converting things to perl_select
 if that’s our end game, but it remains unclear if perl_select is the end
 game—at least how i’m reading all our perl threads.

  Yes, but the OP was asking how to make “perl” be “perl5.18”. That’s the
 kind of thing that “port select” is supposed to be for, except that it
 would conflict with files from the “perl5” port. I don’t think we can
 suggest people use “port select” for perl until the old perl5 port and all
 references to it have been removed.

 Hence why the above is “more work” because if we added the variant we’d
 have to go back and remove it again later. If you really think it’s not
 that big of a problem, then it should be added. I just fear this is another
 instance where we continue kicking the can down the road.

  The other option Daniel advocates is going back to a single perl. That
 would involve even more work, finding all ports that depend on perl5.x or
 any p5.x module, changing them to the one true perl, and also rewriting the
 perl5 portgroup again and all p5 ports and revbumping all of them.

 It would definitely make perl life much easier in the long run. Any of our
 actual perl users should chime in on this one, or if we were using
 statistics we’d know roughly how many users are using our “non-default”
 perls.

  That’s why I proposed the very simple 3-line solution of adding a
 perl5_18 variant to the perl5 port until we decide which way we want to go.

 Yes, but I suspect we won’t be deciding after we add this 3-line solution.
 I’d rather we hammer out our plan than put in an easy temporary fix as
 there is then less emphasis on what needs to be done.

 I’m just really concerned that MacPorts will continue to sit without
 making changes.

 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: changing default perl

[Mark Anderson]

Yeah, that's my gut feeling. Just supporting the latest and greatest Perl
would be fine by me. The accelerated releases of Perl have caused a bit of
an issue - We were stuck with 5.8 for quite some time before the delay of
perl6 started causing a resurgence in interest in developing the perl core.
Perl has a tendency to go out of its way to not break backwards
compatibility to an almost annoying degree, so I would hope the impact
could be minimal. And until Perl6 comes along, the benefit of staying on
5.16 vs. 5.18 is hard to see. When we get to perl6, it will be much like
python 2 vs. 3 and I can see keeping both around.

—Mark
___
Mark E. Anderson e...@emer.net


On Sun, Nov 3, 2013 at 5:44 PM, Clemens Lang c...@macports.org wrote:

 Hi,

 On Sun, Nov 03, 2013 at 05:12:45PM -0500, Mark Anderson wrote:
  I'm all for doing what we need to do. I use a lot of perl, and I have
  always tried to install the latest or close to latest. Back before we
  had the perl5 port I had a perl script that read every port file and
  essentially did this: s/perl5.8/perl5.12/ - so I'm a big fan of having
  the latest available.

 So your opinion is providing a single perl version (the latest stable
 one) would be the way to go?

 To be honest, I don't know why we've ever diverged from this strategy.
 We're in a habit of shipping the latest and greatest version of software
 for most ports we have, sometimes even if breaks dependents (in which
 case we try to fix the dependents or get upstream to fix them for us).
 Maybe somebody who has seen the transition back then can comment on
 that?

 We're in a similar situation for python (and will probably be for php,
 mysql, ...), where we still allow users to install versions that have
 run out of support (even security-related) years ago, but I fear that's
 another can of worms we can open when the perl situation is resolved and
 we've learned our share from doing so.

 I'd advocate for keeping the subport magic, though – there *will* be a
 perl 6 sooner or later, and not throwing away that might simplify this
 transition a lot.

 --
 Clemens Lang


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: changing default perl

[Mark Anderson]

I'm with you there. 5.8 and 5.10 are long out of support. The Perl
community also strongly advises moving to the latest version as soon as it
is marked stable, that's why they make you do things like: use 5.018; to
get new features that can break old ones. Which is why I'm leaning more and
more toward nuking all but the latest perl and away from port select.

—Mark
___
Mark E. Anderson e...@emer.net


On Mon, Nov 4, 2013 at 9:44 AM, Daniel J. Luke dl...@geeklair.net wrote:

 On Nov 3, 2013, at 4:42 PM, Ryan Schmidt ryandes...@macports.org wrote:
  On Nov 3, 2013, at 15:38, Mark Anderson wrote:
  Although we do need to come up with a better perl strategy. The current
 workings drive me crazy.
 
  I’m curious why that is. We use this strategy for PHP and Python as well
 and IMHO it works very well there. Do those drive you crazy also, or is it
 just Perl, and if so, what makes Perl different?

 php/python versions exists because there are substantial changes in the
 language(s) that things written against the older versions not work with
 newer interpreters.

 For perl5 that is largely not the case (there are things that have
 changed, but mostly in backwards-compatible ways).

 perl is also a little different in the wide number of things available on
 CPAN, and the tendency of (many? most?) people working with perl to make
 use of CPAN modules whenever possible.

 I'm not aware of a compelling use-case for keeping many versions of perl5
 around (or at least one that makes sense in the context of MacPorts) -
 while it does make things more complicated for our end-users.

 --
 Daniel J. Luke
 ++
 | * dl...@geeklair.net * |
 | *-- http://www.geeklair.net -* |
 ++
 |   Opinions expressed are mine and do not necessarily   |
 |  reflect the opinions of my employer.  |
 ++




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: changing default perl

[Mark Anderson]

Actually, I kinda like that idea. It will be a lot of work, though. But it
would keep me from having to mix CPAN and p5-* which I know is not
recommended, but I still do.

—Mark
___
Mark E. Anderson e...@emer.net


On Tue, Nov 5, 2013 at 9:46 AM, Daniel J. Luke dl...@geeklair.net wrote:

 I would say we should even go further, and get rid of all of the p5-*
 ports.

 Instead, we should install perl5 as the latest stable perl, and include
 our own 'cpanm' program (like how perlbrew has it's own) which would
 download/build/(test)/install modules (probably into a DESTROOT to allow
 MacPorts to do the actual install and to take advantage of Macports being
 able to do unininstall). We could add a new dependency type (and associated
 functionality) to allow ports to still depend on perl modules, and the
 perl5 port could uninstall/reinstall all of the installed perl modules when
 upgraded (or actually, on post-activate).

 Of course, that's considerably more work (and requires changes to base/
 that others may or may not be willing to accept into base/).

 We should at least just switch to one stable perl5, though.

 On Nov 4, 2013, at 7:05 PM, Mark Anderson e...@emer.net wrote:
  I'm with you there. 5.8 and 5.10 are long out of support. The Perl
 community also strongly advises moving to the latest version as soon as it
 is marked stable, that's why they make you do things like: use 5.018; to
 get new features that can break old ones. Which is why I'm leaning more and
 more toward nuking all but the latest perl and away from port select.

 --
 Daniel J. Luke
 ++
 | * dl...@geeklair.net * |
 | *-- http://www.geeklair.net -* |
 ++
 |   Opinions expressed are mine and do not necessarily   |
 |  reflect the opinions of my employer.  |
 ++




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: changing default perl

[Mark Anderson]

Yeah, I'd apply that patch while we all figure out what to do. I'd be happy
to take on the Perl fixing work as Perl is my first language love. (Well
C/C++ I learned first, so I guess, my first scripting language love.
Technically, I learned BASIC on a TI/994A first, but the less said about
that the better.)

I'd probably need a branch to start doing that, though. I can't imagine
we'd want to do that on trunk.

—Mark
___
Mark E. Anderson e...@emer.net


On Sun, Nov 10, 2013 at 1:28 PM, Lawrence Velázquez lar...@macports.orgwrote:

 On Nov 10, 2013, at 12:05 PM, Puneet Kishor punk.k...@gmail.com wrote:

  Sadly, I need to use something later than perl 5.12. If I can't use
 Macports perl, I would have to install a new version using Perlbrew (or
 some other mechanism). Is there anything I can do for now to get with using
 the Macports perl 5.18 rightaway?

 You can install perl5.14, perl5.16, and perl5.18 whenever you'd like.

 If you absolutely require perl5, you could create a local portfile
 repository[1] and apply the  +perl5_18 patch[2] yourself.

 [1]
 http://guide.macports.org/chunked/development.local-repositories.html
 [2]
 https://trac.macports.org/attachment/ticket/41160/perl5-Portfile.diff

 vq

 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: changing default perl

[Mark Anderson]

I love the idea of a portfile override, but building from cpanm (cpanmp?)
most of the time.

—Mark
___
Mark E. Anderson e...@emer.net


On Mon, Nov 11, 2013 at 11:44 AM, Daniel J. Luke dl...@geeklair.net wrote:

 On Nov 11, 2013, at 11:32 AM, Ryan Schmidt ryandes...@macports.org
 wrote:
 
  It would certainly be possible to have some local metadata that our
 cpanm could consult to do any of the above, though.
 
  This sounds like inventing a second language to do what we can already
 do in portfiles.

 I guess it could be implemented that way, but it's not really what I was
 thinking.

  I like Jeremy’s idea of adding a portfile only if necessary to fix
 issues (add patches, etc.).

 that would probably work.

  The main benefit would be that /all/ of the modules would be available
 in a MacPorts supported way and they would be up-to-date without an army of
 volunteers building cookie-cutter portfiles for them.
 
  And that would be great!
 
  If we do this, we should find a way to make it abstract so that we can
 integrate other package managers besides CPAN. For example we have the same
 problem for php’s PEAR package manager: two years ago, Bradley put all of
 PEAR in MacPorts, but it hasn’t been updated since then. Perhaps this
 functionality could still be implemented as portgroups, or at least as tcl
 files in the _resources directory, so that new MacPorts base releases are
 not needed to make changes there.

 I don't really know how other languages do this (and I'm no php expert).
 I'm at least somewhat leery of trying to design the most generic solution
 for this too (I would much rather make something that works and extend it
 if it seems reasonable to do so).

 I think we require base/ changes if only because there won't necessarily
 be a portfile for each perl module yet there are going to be ports that
 depend on some of these modules (so we would need a way to handle that).

 also - having to create releases to add functionality really shouldn't be
 something that we try to hack around by pushing code some other way. Does
 our release process need some attention to make it easier to do?

 --
 Daniel J. Luke
 ++
 | * dl...@geeklair.net * |
 | *-- http://www.geeklair.net -* |
 ++
 |   Opinions expressed are mine and do not necessarily   |
 |  reflect the opinions of my employer.  |
 ++




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: fife Unknown Horizons Game

[Mark Anderson]

I tried sometime ago, fife is not the easiest thing to build on the mac.
But I'd be willing to help out. If you can help figure out how to get it to
compile, we can make a port file.

—Mark
___
Mark E. Anderson e...@emer.net


On Sun, Dec 8, 2013 at 5:05 PM, Jean-François Caron jfca...@phas.ubc.cawrote:

 Hi, I am wondering if anyone with the skill is able to try updating 
 fixing the port fife.  The current version is at 0.3.1 and the latest is
 0.3.6-ish, and a cool-looking game needs at least 0.3.4 (Unknown Horizons).
  fife also doesn't build, I get the same error as here:
 https://trac.macports.org/ticket/39581.

 According to the game devs for Unknown Horizons, getting fife installed on
 a Mac is the major obstacle to people trying the game on Macs.  If fife
 could be made to work again, then there would be the potential to create a
 new port for the Unknown Horizons game itself, which would be very exciting.

 http://www.unknown-horizons.org/

 The people on #unknown-horizons on freenode seem to be very willing to
 help, but I think I'm over my head just trying to compile the thing myself,
 yet alone fixing a portfile.

 Jean-François
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Problem with Macports, homebrew, and ghostscript

[Mark Anderson]

It's possible to get Fink and MacPorts to work together, although I don't
recommend it. Before we had ROOT in MacPorts, my wife and I got this to
work on her machine for Particle Physics-y things. Homebrew however, does
not really work and play well with others. If you want to use it, you
really can't use anything else. As for the stuff in usr/local - I'd move it
as everyone is suggesting, and then build everything with MacPorts that you
can. For instance, we have a ports for texlive that will install pretty
much any amount of texlive you want.

Mark

—Mark
___
Mark E. Anderson e...@emer.net


On Wed, Feb 12, 2014 at 3:56 AM, Ryan Schmidt ryandes...@macports.orgwrote:

 You replied only to me. Remember to use the Reply All button in your email
 program to reply to the group also. I’ve re-added the group address to this
 reply.


 On Feb 12, 2014, at 01:37, macosforge.99.ky...@spamgourmet.com wrote:

  Thank you for responding to my query（not sure if this reply is going to
 you or the entire group???). Yes, I would like give up on homebrew and
 stick with macport...I was led into using it without realizing the
 consequences. I have no idea which is better or which I need,
 
  but I am not adept enough at unix to figure out what I will need to do
 do/check to make sure removing homebrew  doesn't mess up things worse.
 Right now everything except vietOCR seems to be working just fine, and I
 don't want to mess it up. As far as computers go, I am porting from
 windows, and  just beginning to catch up on all the ins and outs of how
 linux does things, and sometimes it throws me a surprise
 
  am I right that you are implying if I uninstall homebrew I will not mess
 up ports, e.g. ghostscript, installed via macport? That was key number one.

 Hopefully removing the software you have in /usr/local would not cause
 problems for software you installed using MacPorts, but I cannot guarantee
 that. The problem is that by installing software in /usr/local (whether by
 using Homebrew or other means), other software you build (including
 software build using MacPorts) may find that software in /usr/local and use
 it. This is why we do not support installing software in /usr/local while
 using MacPorts: because it leads to unpredictable results and sometimes
 problems.


  At the least I would like to properly deal with the ghostscript
 9.0.7...I need to figure out why homebrew didn't link...I would like ot
 know if I uninstall it will it also uninstall 9.0.5 (as it usually would in
 windows)
  I was able to figure out via terminal that opt/local/bin is ghostscript
 9.10
  and that usr/local/bin/gs is 9.5
  and 9.7 is in /usr/local/Cellar/ghostscript/9.07/bin/gs, which I assume
 is the unlinked brew, and that 9.5 must have been an old brew. I only
 installed it because I didn't know I already had ghostscript.

 I have never used Homebrew so I do not know how it works. I recommend you
 consult Homebrew documentation for instructions on how to uninstall
 Homebrew and anything you installed with it, if you would like to use
 MacPorts instead. Otherwise, consult the MacPorts Guide for instructions on
 uninstalling MacPorts so that you can instead use Homebrew.


  Generally I don't mind uninstalling homebrew, but I can see that
 usr/local/bin has some things/formulas that don't seem to come from
 homebrew, specifically the  texlive-2013 I just installed via the pkg seems
 to have landed in usr/local/texlive. Also, I see directories for QT and
 macGPG2. So my next question is what do I do about these?

 I recommend you remove anything in /usr/local to ensure you do not
 introduce problems for software built using MacPorts. If removing
 /usr/local reveals that problems were already introduced for software you
 previously built using MacPorts, rebuild those MacPorts ports, for example
 using rev-upgrade as suggested earlier in this thread.


  Can they coexist/be installed with macports? If not, should I move to
 homebrew, except I have quite a bit installed via macports, and would ahve
 to install all these via homebrew, correct??

 As a manager of the MacPorts project, and having not used any other OS X
 package manager in many many years, I of course recommend you use MacPorts.
 If there’s anything Homebrew is doing for you that MacPorts isn’t, please
 let us know so that we can investigate whether we can improve MacPorts to
 meet your needs. For example, if individual software packages you need are
 not in MacPorts, file port request tickets in our issue tracker.


 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Problem with Macports, homebrew, and ghostscript

[Mark Anderson]

They've really started to run into the same problems that MacPorts solved
long ago. Considering the their page title is Homebrew -- MacPorts driving
you to drink? Try Homebrew!, I find pleasure in their difficulty. The only
thing I wish we did that they do is git. But we don't forbid it, so eh.

--Mark
___
Mark E. Anderson e...@emer.net


On Wed, Feb 12, 2014 at 8:44 AM, Arno Hautala a...@alum.wpi.edu wrote:

 On Tue, Feb 11, 2014 at 4:12 PM, Art McGee amc...@gmail.com wrote:
  Homebrew is mainly intended to be used by developers who use their system
  almost exclusively for development. They are unconcerned with the
 effects of
  mucking with /usr/local and it's ownership or permissions.

 I know this is getting off topic, but I disagree with this assessment.
 While I'm sure there are developers that use Homebrew, I think the
 primary audience is the average user who just wants it to work (I'm
 sure that demographic includes developers as well). Specifically, the
 user who doesn't understand why MacPorts is taking so long to install
 so many things when all they want is one tool. They're probably
 already running as an administrator and are the only user on the
 system, so who cares if /usr/local is set world writeable? From a
 certain point of view, that seems valid, but it does ignore the
 reasons that led to MacPorts' complexity and the steps that MacPorts
 has taken to mitigate some of those concerns (ie. pre-built packages).

 --
 arno  s  hautala/-|   a...@alum.wpi.edu

 pgp b2c9d448
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript

[Mark Anderson]

I also install into /opt/something where something expands to something
descriptive of all the crap I am installing in there. Then I can turn PATHs
on and off depending. This is really important for playing with things like
the gtk+ cocoa that needs its whole space to itself. Just DONT use /opt or
/opt/local of course. I also set them to be owned by my user, so I don't
have to sudo to install. If I do, I know something is up.

Mark

--Mark
___
Mark E. Anderson e...@emer.net


On Wed, Feb 12, 2014 at 10:56 AM, Arno Hautala a...@alum.wpi.edu wrote:

 On Wed, Feb 12, 2014 at 10:04 AM, Gregory Shenaut gkshen...@ucdavis.edu
 wrote:
  I understand why installing in /usr/local can mess up macports, but
 macports doesn't have everything, and most third-party software wants to go
 into /usr/local. Where should this stuff go, if not /usr/local?

 I install everything into my home folder.

  ./configure --prefix=~/local/
  make  make install

 If you need it available system-wide, just pick some other custom
 location (ie. /custom/). In any case, just make sure you're consistent
 (update your PATH) and point your configure script to the right place
 if the software can't find the libraries in your path or you need to
 override libraries that are in your path.

 The longer answer is that I use stow
 (http://www.gnu.org/software/stow/ ; and available in MacPorts) to
 assemble the bin, man, etc. directories. Stow isn't required, but it
 does help manage the software that isn't being managed by MacPorts.
 So, I might install a piece of software with:

  ./configure --prefix=~/local/stow/foo-1.2.4
  make  make install
  cd ~/local/stow
  stow foo-1.2.4

 Stow just allows you to easily add and remove versions of software by
 linking a hiearchy of directories into a common location. I might have
 foo-1.2.4, foo-1.2.6, bar-3.9, but only have foo-1.2.4 and bar-3.9
 active. I can the upgrade to foo-1.2.6 by running:

  cd ~/local/stow
  stow -D foo-1.2.4
  stow foo-1.2.6
  rm -rf foo-1.2.4


 --
 arno  s  hautala/-|   a...@alum.wpi.edu

 pgp b2c9d448
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: usage numbers for macports vs. homebrew?

[Mark Anderson]

Yeah, I think tcl is one of the things that confounds people the most. Not
really learned that much anymore. I learned it long ago for CAD tools from
IBM.

But really, both Homebrew and Macports are domain specific languages from
the port writers perspective. You've got to learn it anyway. People in my
CS department lab would go to Homebrew first and then come ask me how to
install MacPorts since we have much better package selection.

For instance: If I type brew search tex, it recommends installing MacTex
instead of a from-source install. LAME.

Mark

--Mark
___
Mark E. Anderson e...@emer.net


On Tue, Mar 18, 2014 at 3:04 PM, Daniel J. Luke dl...@geeklair.net wrote:

 On Mar 18, 2014, at 3:01 PM, Ryan Schmidt ryandes...@macports.org wrote:
 
  On Mar 18, 2014, at 12:54, Daniel J. Luke dl...@geeklair.net wrote:
  GitHub plus not having to learn/use tcl seem to be the major features
 that pull people/create interest from what I've seen (but I haven't looked
 in on it in a while).
 
  ...right, instead of you have to learn/use ruby. Six of one...

 'ruby' has been pretty hot for a while and 'tcl' (and perl, and php) is
 considered lame.

 (note that I'm not saying I personally agree with that assessment).

 --
 Daniel J. Luke
 ++
 | * dl...@geeklair.net * |
 | *-- http://www.geeklair.net -* |
 ++
 |   Opinions expressed are mine and do not necessarily   |
 |  reflect the opinions of my employer.  |
 ++



 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: usage numbers for macports vs. homebrew?

[Mark Anderson]

On Tue, Mar 18, 2014 at 3:27 PM, Landon Fuller land...@macports.org wrote:

 MacPorts driving you to drink?


I hate that. Turned me off the whole project.

--Mark
___
Mark E. Anderson e...@emer.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: handbrake?

[Mark Anderson]

I just started looking at it. Whew. That is a quite a Portfile. We should
file a ticket to get it to 0.10.0, but as it's nomaintainer, I doubt anyone
will mind you working on it. In fact, I'd encourage it.

—Mark
___
Mark E. Anderson e...@emer.net

On Sun, Jan 25, 2015 at 4:52 PM, Craig Treleaven ctrelea...@macports.org
wrote:

 At 11:39 AM -0800 1/25/15, Ludwig wrote:

 Is any work being done on the broken Handbrake port?  It's been over a
 year
 since the last revision.  I'll see what I can do with it, but I don't
 want to
 step on toes or duplicate effort.


 There is no official maintainer for the port although I see larryv owns
 one of the tickets.

 https://trac.macports.org/query?status=assignedstatus=
 newstatus=reopenedport=~handbrakeorder=priority

 I suspect that patches are welcome!

 Long ago, I looked at the port but quickly ran away due to the lengthy
 list of standard libraries where it fetches and builds its own version.
 Potentially, you get to deal with any or all of the MacPorts-related issues
 that has been faced for each of those libraries.  Not my idea of fun.

 Craig

 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: handbrake?

[Mark Anderson]

That port is a beast. I'm amazed it ever worked.

—Mark
___
Mark E. Anderson e...@emer.net

On Mon, Jan 26, 2015 at 11:15 AM, Lawrence Velázquez lar...@macports.org
wrote:

 On Jan 25, 2015, at 2:39 PM, Ludwig macpo...@metaspasm.org wrote:

  Is any work being done on the broken Handbrake port?  It's been over a
 year
  since the last revision.  I'll see what I can do with it, but I don't
 want to
  step on toes or duplicate effort.

 I have been working on this for the past couple of weeks; if anyone's been
 wondering why I've been committing infrequently lately, this is why. Turns
 out that wrangling 19 build systems in one port is not particularly simple.

 vq
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: New Mac OS Forge administrator

[Mark Anderson]

Oh thank god. I was afraid MacOSForge was circling the drain.

—Mark
___
Mark E. Anderson 

On Fri, Nov 20, 2015 at 6:23 PM, Eneko Gotzon  wrote:

>
> On Fri, Nov 20, 2015 at 10:03 PM, Ian Wadham  wrote:
>
>> find some time to answer queries on the list…
>>
> I have learned so much from your posts…
>>
>
> +1
>
> Thank you Ryan!
>
> Best wishes!!
>
> --
> Eneko Gotzon Ares
> enekogot...@gmail.com
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports fails to build in macOS 10.12 Sierra

[Mark Anderson]

Thanks a bunch for the info. I'll talk to my WWDR - this bit has always
confused me. I wish I had thought of it at WWDC, we had a meeting last
week. I usually just talk to people in the dev program anyway, but I'd like
to know what help I can give and how publicly.

—Mark
___
Mark E. Anderson <e...@emer.net>

On Sun, Jun 19, 2016 at 11:52 PM, Jeremy Huddleston Sequoia <
jerem...@apple.com> wrote:

>
> > On Jun 19, 2016, at 17:15, Mark Anderson <e...@emer.net> wrote:
> >
> > Jeremy, I'm still interested in a answer as to what is covered by this:
> >
> > Further, Apple agrees that You will not be bound by the foregoing
> confidentiality terms with regard to technical information about
> pre-release Apple Software and services disclosed by Apple at WWDC (Apple’s
> Worldwide Developers Conference), except that You may not post screenshots,
> write public reviews or redistribute any pre-release Apple Software or
> services.
> >
> > Genuinely, not sarcastically or politically. I have no interest in
> losing my developer program membership. What about Sierra and iOS 10 can we
> talk about based on this clause? I had thought it was stuff like this, but
> I appear to have been mistaken.
>
> Hey Mark,
>
> My personal and unaffiliated (Apple hat is off) strict interpretation of
> this is that you can discuss anything that was made publicly available by
> Apple through public announcements but nothing more.  In the past, these
> restrictions were much tighter, but they have loosened up quite a bit over
> the past few years alongside the public betas.  I suggest you reach out to
> Apple WWDR for clarification on the terms if you are uncertain (and I would
> be extremely happy to be wrong if they state otherwise), but it's always
> good to be on the safe side.  As someone else mentioned on the thread,
> Apple did not disclose MacPorts interoperability with Sierra, so a strict
> interpretation of the agreement would suggest keeping a lid on it with
> respect to MacPorts and filing radars at http://bugreport.apple.com for
> any compatibility issue you run into (and I'd welcome getting pinged about
> such issues, so I can look into them personally).
>
> Also note that in the past, such restrictions loosened once the first
> public beta was made available, so it's possible that such open discussion
> will be ok once that happens.
>
> --Jeremy
>
> >
> > —Mark
> > ___
> > Mark E. Anderson <e...@emer.net>
> >
> > On Sun, Jun 19, 2016 at 5:16 PM, Jeremy Sequoia <jerem...@apple.com>
> wrote:
> >
> >
> > Sent from my iPhone...
> >
> > > On Jun 19, 2016, at 13:55, Bachsau <w...@bachsau.name> wrote:
> > >
> > >
> > >> Am 19.06.2016 um 05:24 schrieb Jeremy Huddleston Sequoia <
> jerem...@apple.com>:
> > >>
> > >> As a reminder, macOS 10.12 Sierra has only been released as a
> developer preview to developers and is covered by an NDA.
> > >
> > > Ever heard of something called "free speech"? The snowden leaks were
> also covered by an NDA an we know what it led to.
> >
> > I suggest you consult with a lawyer to learn a bit about those terms,
> and they can explain to you that NDAs are not a violation of one's first
> amendment rights.
> >
> > Because of his well informed choice, Snowden basically lost his freedom
> of movement and is confined to "living on the Internet" (in Russia).  While
> the same won't happen here and your analogy is quite laughable, it is
> important for developers to remember the agreements that they have signed
> and honor their word if they expect others to trust them in the future.
> Most violations (like this) are simply accidental and developers for the
> most part want to honor the agreement and appreciate such clarifications
> and reminders.  Egregious and intentional violations of the NDA have in the
> past resulted in termination of the developer relationship with Apple which
> can be quite damaging to a developer's livelihood.  I'm just trying to help
> protect the developers that want to honor their word.
> > ___
> > macports-users mailing list
> > macports-users@lists.macosforge.org
> > https://lists.macosforge.org/mailman/listinfo/macports-users
> >
> > ___
> > macports-users mailing list
> > macports-users@lists.macosforge.org
> > https://lists.macosforge.org/mailman/listinfo/macports-users
>
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports fails to build in macOS 10.12 Sierra

[Mark Anderson]

Jeremy, I'm still interested in a answer as to what is covered by this:

Further, Apple agrees that You will not be bound by the foregoing
confidentiality terms with regard to technical information about
pre-release Apple Software and services disclosed by Apple at WWDC (Apple’s
Worldwide Developers Conference), except that You may not post screenshots,
write public reviews or redistribute any pre-release Apple Software or
services.

Genuinely, not sarcastically or politically. I have no interest in losing
my developer program membership. What about Sierra and iOS 10 can we talk
about based on this clause? I had thought it was stuff like this, but I
appear to have been mistaken.

—Mark
___
Mark E. Anderson 

On Sun, Jun 19, 2016 at 5:16 PM, Jeremy Sequoia  wrote:

>
>
> Sent from my iPhone...
>
> > On Jun 19, 2016, at 13:55, Bachsau  wrote:
> >
> >
> >> Am 19.06.2016 um 05:24 schrieb Jeremy Huddleston Sequoia <
> jerem...@apple.com>:
> >>
> >> As a reminder, macOS 10.12 Sierra has only been released as a developer
> preview to developers and is covered by an NDA.
> >
> > Ever heard of something called "free speech"? The snowden leaks were
> also covered by an NDA an we know what it led to.
>
> I suggest you consult with a lawyer to learn a bit about those terms, and
> they can explain to you that NDAs are not a violation of one's first
> amendment rights.
>
> Because of his well informed choice, Snowden basically lost his freedom of
> movement and is confined to "living on the Internet" (in Russia).  While
> the same won't happen here and your analogy is quite laughable, it is
> important for developers to remember the agreements that they have signed
> and honor their word if they expect others to trust them in the future.
> Most violations (like this) are simply accidental and developers for the
> most part want to honor the agreement and appreciate such clarifications
> and reminders.  Egregious and intentional violations of the NDA have in the
> past resulted in termination of the developer relationship with Apple which
> can be quite damaging to a developer's livelihood.  I'm just trying to help
> protect the developers that want to honor their word.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Can brew and port be used on the same system?

[Mark Anderson]

Yes, but I'd advise against it. I thought I had to for RVM and it caused me
loads of trouble. Then I learned I could set it to MacPorts and a deleted
brew and never looked back. I've been using MacPorts since before Intel, so
I'm attached.

—Mark
___
Mark E. Anderson 

On Sat, May 27, 2017 at 10:22 PM, Al Varnell  wrote:

> I'm told it can be done now, but can get messy. I gave up on brew several
> years ago. Too many conflicts back then.
>
> Sent from Janet's iPad
>
> -Al-
> --
> Al Varnell
> Mountain View, CA
>
> On May 27, 2017, at 7:13 PM, Michael  wrote:
> > So apparently the open source code version of Jedi Knights Academy and
> Outcast https://github.com/JACoders/OpenJK rely on brew's SDL 2, and have
> that installation pathname in their binaries.
> >
> > Can I install brew, with its use of /usr/local/, at the same time as
> ports?
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users