Re: How to use git

[Mark Anderson]

I use git (and Github Enterprise) in my day to day work. I can help out.

Another good (free (as in beer)) client is SourceTree
https://www.sourcetreeapp.com/

—Mark
___
Mark E. Anderson 

On Fri, Aug 19, 2016 at 8:19 PM, Ryan Schmidt 
wrote:

> Here are some resources GitHub recommends for learning git:
>
> https://help.github.com/articles/good-resources-for-
> learning-git-and-github/
>
> When MacPorts moves to GitHub, committers will need to stop using their
> existing Subversion working copies and get a fresh copy of the code from
> GitHub. There will be separate repositories for base, ports, the web site,
> and so forth.
>
> If you are a committer or would like to contribute to MacPorts in the
> future, and you don't already have a GitHub account, you should create one
> now. If you are a committer, you should add your @macports.org email
> address
> to your GitHub account now, so that any past commits you made in Subversion
> are properly associated with your GitHub account.
>
> Some of our developers are not very, or not at all, familiar with how to
> use
> git, and I include myself in that list. It would be great if we could
> prepare a wiki page that helps Subversion users learn to use git, perhaps
> with examples such as "In Subversion, to update your working copy with the
> latest code, you run 'svn update', while with git, you update your clone
> using 'git pull'". We may also need some task-related examples, such as how
> to create a new port; how to update an existing port; how to install an
> updated version of a port that was submitted as a pull request; how to fix
> a
> pull request that isn't quite correct. We may also need some explanations
> of
> git terminology, such as "master", "origin", "rebase", "fast-forward", etc.
> Let's use this wiki page to collect this information:
>
> https://trac.macports.org/wiki/WorkingWithGit
>
> If you aren't familiar with git, please ask specific questions about tasks
> that you don't know how to do in git. If you are familiar with git, please
> help answer these questions.
>
> GitHub offers a nice Mac app that makes it easy to do basic tasks like
> committing updates without having to know how to use git on the command
> line.
>
> GitHub also offers a Subversion compatibility feature. If you don't know
> git
> and don't want to learn right now, you can continue to use the Subversion
> client as before, you'll just have to "svn checkout" a new working copy
> from
> the GitHub repository URL. You can use that working copy with your normal
> Subversion client and it should behave as a normal Subversion repository.
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Goodbye Mac OS Forge, hello GitHub

[Mark Anderson]

Yeah, no one wants Github to be the new SF. Thankfully, git helps there, we
can pick up and move anytime. Also, it's a bit less once size fits all
thing than SF. SF had everything. Github is more focused. The lack of ads
and the pay to play system makes me feel better about it.

—Mark
___
Mark E. Anderson 

On Fri, Aug 19, 2016 at 9:04 PM, Kevin Walzer  wrote:

> On 8/19/16 8:18 PM, Ryan Schmidt wrote:
>
>> Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the
>> decade since Mac OS Forge was created, collaborative software development
>> platforms like GitHub and BitBucket have become very popular and
>> successful,
>> and when I was hired as Mac OS Forge sysadmin last year, part of my job
>> was
>> to evaluate whether such services could be a suitable replacement for
>> those
>> offered by Mac OS Forge. We determined that the answer was yes, and that
>> GitHub was the best choice, due to its overwhelming popularity. Other Mac
>> OS
>> Forge projects including XQuartz, CUPS and CalendarServer are already in
>> the
>> process of moving to GitHub, and the time has now come for MacPorts to
>> likewise bid a fond farewell to Mac OS Forge and move on.
>>
>
> This is certainly an interesting development. I hope this works out well
> for the MacPorts project. What will become of MacOS Forge if all its
> projects migrate off it? Is Apple ceasing support for MacOS Forge?
>
> I understand that a lot of thought has gone into this decision, but it's
> also not hard to view one of its primary motivators--"all the cool projects
> are on Github, and it's crucial for developer mindshare"--as something to
> view with concern. Competition in this space is healthy. A decade ago
> SourceForge occupied the place in the community that Github does now, and
> there was hardly any place else to go if their site was down. One reason
> Tcl/Tk moved off SF to their own Fossil repo was because of a serious
> outage at the site that prevented commits for weeks.
>
> This is more of a hope that Github does not become the kind of monoculture
> that SF was than any criticism of Github--as long as Bitbucket and other
> platforms are around and still have some volume, that will help.
>
> --Kevin
>
> --
> Kevin Walzer
> Code by Kevin/Mobile Code by Kevin
> http://www.codebykevin.com
> http://www.wtmobilesoftware.com
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Goodbye Mac OS Forge, hello GitHub

[Mark Anderson]

This is super exciting. I can ditch my weird github workflow and have my
own proper fork. And I agree, github issues really are terrible, glad to
see we're sticking with trac.

—Mark
___
Mark E. Anderson 

On Fri, Aug 19, 2016 at 8:28 PM, C. R. Oldham  wrote:

>
>
>
> On August 19, 2016 at 6:19:06 PM, Ryan Schmidt (ryandes...@macports.org)
> wrote:
>
> I'm pleased to announce that MacPorts will be moving its source code to
> GitHub.
>
> This is fantastic and phenomenal.
>
> Does this mean that updates to ports can be submitted via GitHub Pull
> Request?
>
>
> --cro
>
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: What to do with old versions of Python, Perl, PHP, Apache1 (and others)?

[Mark Anderson]

I vote for killing a lot of them. Apache 1 for instance is a very bad thing
to be running right now. If they are EOL upstream, keeping them around is
also a bit of false hope to people that might need them. I know I for one
could not fix some of these builds since I don't have old enough OSes, and
I don't really care to.

—Mark
___
Mark E. Anderson 

On Thu, Feb 4, 2016 at 5:47 PM, Jeremy Lavergne 
wrote:

> On 02/04/2016 03:32 PM, Joshua Root wrote:
> >> The question is: what should be the general policy with these ports?
> >> How long should we keep them around?
> >
> > As long as they still build on some OS X version that base works on. If
> > they break and nobody steps up to fix them, that's a pretty good
> > indication that it's time for them to go.
> >
> > As you mentioned, there are all kinds of reasons why people have to test
> > against old versions. A deprecation warning in the description and notes
> > would be a good idea.
>
>
> Could this be considered reinforcing the expectation of no one fixing
> tickets?
>
> If people need to use the very old versions, we should encourage them to
> use source control to look up these Portfiles. While stubbing ports with
> this message would be helpful, I worry how many ports would become stubs.
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

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-us...@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Owner of MacPorts account on GitHub

[Mark Anderson]

Feels like MacOSForge is circling the drain. XQuartz left. Now we're having
nothing but trouble.

—Mark
___
Mark E. Anderson 

On Tue, Nov 10, 2015 at 11:57 PM, Mojca Miklavec  wrote:

> On Wed, Nov 11, 2015 at 12:58 AM, Lawrence Velázquez wrote:
> > On Nov 9, 2015, at 4:45 PM, Rainer Müller wrote:
> >
> >> On 2015-11-09 21:01, Mojca Miklavec wrote:
> >>> Does anyone know who owns
> >>>https://github.com/MacPorts
> >>> ?
> >>
> >> I would be interested to know that as well. I actually found a way to
> >> send them a message last week. Now we can just wait for them to get back
> >> to us.
> >
> > Surprise! It's me.
>
> Great.
>
> Is there any chance that we put mirrors of the SVN repository there?
>
> I would suggest to use these for simplicity:
> https://www.macosforge.org/post/git-mirrors/
> but since they are not up to date anyway, it would be better to make
> new ones from scratch and also include a semi-hand-crafted authors
> transformation file.
>
> > I've been waiting 2 years 6 months 18 days for this. Thought it might
> never happen.
>
> At the moment it's the lack of Trac's functionality to browse the tree
> and the logs that has triggered the "demand" for this.
>
> Mojca
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Plan B?

[Mark Anderson]

I dunno, but it seems like we're easily the most active project on here.
Followed by XQuartz maybe. All this down time certainly makes me nervous.

—Mark
___
Mark E. Anderson 

On Mon, Oct 12, 2015 at 10:51 AM, Daniel J. Luke  wrote:

> On Oct 12, 2015, at 5:49 AM, Mojca Miklavec  wrote:
> > I hate to ask that question and I'm not trying to suggest moving away
> > just yet, but what is our plan B in case of some critical server
> > failures?
>
> I believe portmgr has said that they’ve discussed it.
>
> > Do we have a backup plan or plan B? Are we able to move the services
> > elsewhere if the current hosting becomes seriously broken one day,
> > possibly without any prior notice?
>
> The project controls the domain registration, so in a ’worst case
> scenario' we could move the domain and set up ‘new’ stuff.
>
> > I don't want to start panicking, but it would be nice to have a
> > backup/read-only mirror of trac and the main website somewhere. And
> > possibly backups of other services.
>
> I’d like to know if Apple isn’t interested in hosting for us anymore and
> if we should maybe look to do an orderly transition to somewhere else (or
> if something is changing to fix the lack of attention to problems that
> we’re currently seeing).
>
> —
> 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-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Looking for some testers for Pallet

[Mark Anderson]

Sorry, I mean 10.11, and I'm looking for 10.10 to test on. Classic off by
one.

—Mark
___
Mark E. Anderson 

On Mon, Jul 20, 2015 at 7:31 PM, Mark Anderson  wrote:

> Quick update on what I saw, on 10.10 it dies due to lack of 10.8 SDK and
> once I fixed that, garbage collection is not supported so Xcode 7 will not
> compile it. Obviously not a direct problem now, but will be shortly.
>
> I'm going to see if I can dig up a 10.9 machine image to test on.
>
>
> —Mark
> ___
> Mark E. Anderson 
>
> On Mon, Jul 20, 2015 at 2:45 PM, Kyle Sammons 
> wrote:
>
>> Hey everyone,
>>
>> The progress on Pallet is now around the point where I need some other
>> people to try to run it, to make sure it's building and running correctly
>> on other systems. If you're interested in doing so, I've included the
>> details on how to build and run it below (8 to 9 total steps):
>>
>> Generating a self-signed certificate (Only have to do this once):
>> 1. Go to KeyChain Access
>> 2. Click on KeyChain Access -> Certificate Assistant -> Create A
>> Certificate...
>> 3. Set the name to, "Self-signed Applications", without quotes.
>> 4. Set the Identity Type to "Self Signed Root"
>> 5. Set the Certificate Type to, "Code Signing"
>> 6. Hit "Create"
>>
>> Pulling the code:
>> 1. Create a new directory to put the code into (personal preference,
>> really)
>> 2. Run, "svn checkout
>> https://svn.macports.org/repository/macports/branches/gsoc15-pallet";
>>
>> Building and running:
>> 1. Run, "sudo sh build_and_run.sh", and if everything went correctly, it
>> should build and begin running Pallet!
>>
>> If anything goes wrong (or right), if you could please tell me what
>> happened, that'd be greatly appreciated!
>>
>> Thanks,
>> -Kyle
>>
>> ___
>> macports-dev mailing list
>> macports-dev@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
>>
>>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Looking for some testers for Pallet

[Mark Anderson]

Quick update on what I saw, on 10.10 it dies due to lack of 10.8 SDK and
once I fixed that, garbage collection is not supported so Xcode 7 will not
compile it. Obviously not a direct problem now, but will be shortly.

I'm going to see if I can dig up a 10.9 machine image to test on.


—Mark
___
Mark E. Anderson 

On Mon, Jul 20, 2015 at 2:45 PM, Kyle Sammons  wrote:

> Hey everyone,
>
> The progress on Pallet is now around the point where I need some other
> people to try to run it, to make sure it's building and running correctly
> on other systems. If you're interested in doing so, I've included the
> details on how to build and run it below (8 to 9 total steps):
>
> Generating a self-signed certificate (Only have to do this once):
> 1. Go to KeyChain Access
> 2. Click on KeyChain Access -> Certificate Assistant -> Create A
> Certificate...
> 3. Set the name to, "Self-signed Applications", without quotes.
> 4. Set the Identity Type to "Self Signed Root"
> 5. Set the Certificate Type to, "Code Signing"
> 6. Hit "Create"
>
> Pulling the code:
> 1. Create a new directory to put the code into (personal preference,
> really)
> 2. Run, "svn checkout
> https://svn.macports.org/repository/macports/branches/gsoc15-pallet";
>
> Building and running:
> 1. Run, "sudo sh build_and_run.sh", and if everything went correctly, it
> should build and begin running Pallet!
>
> If anything goes wrong (or right), if you could please tell me what
> happened, that'd be greatly appreciated!
>
> Thanks,
> -Kyle
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Migrating to Perl 5.20/5.22

[Mark Anderson]

I second perl 5.22. And that we should only support the latest perl.

—Mark
___
Mark E. Anderson 

On Tue, Jul 14, 2015 at 5:39 PM, Daniel J. Luke  wrote:

> > On Jul 14, 2015, at 12:22 PM, David Evans  wrote:
> > My point in being cautious has to do with fact that perl5.22 has just
> recently been released as the latest stable version.
>
> this is criteria we don’t have in general for any other ports.
>
> If upstream says it’s stable, it’s what we provide in almost all cases.
>
> > I have confidence in perl5.22
> > itself but the fact that it is stable says nothing about whether the
> various Perl modules work with it properly.
>
> traditionally, we find out when things break by people complaining - as a
> project we don’t do a lot of proactive testing.
>
> > They are completely untested on Macports
> > with respect to this version other than to say that they build. Because
> of the apathy towards supporting Perl modules, in general, by the MacPorts
> maintainer community (952/1373 modules are nomaintainer), the only time
> modules actually get tested is when they are updated.  Maybe.
> >
> > And this testing is really cursory.
>
> we should set up something to run the automated test suite included with
> almost every module.
>
> We should probably get out of the business of perl module portfiles
> entirely, too.
>
> > I am concerned that switching to perl5.22 immediately will inevitably
> cause unexpected consequences in terms of module useability.
>
> most things will probably work, some things are probably already broken,
> anything remaining is somewhat reasonable to fix as people report it.
>
> > My compromise proposal is to switch to perl5.20 as the default now and
> drop all Perl versions except perl5.20 and perl5.22.  Then plan to drop
> perl5.20
> > in say three to six months, after there is time for upstream module
> maintainers to address remaining perl5.22 issues, and leave perl5.22 as the
> sole Perl version supported.
>
> I’m not volunteering to do this work, so I guess if you’re willing to do
> it - go for it.
>
> > After that, update the sole Perl port not at the time of the next stable
> period, but, again, 3 to 6 months thereafter for the same reasons.
>
> I would strongly recommend we don’t add lag time here - just update the
> perl port once its released and update/patch modules if they turn out to be
> broken. Module authors/people who use the modules have some responsibility
> to keep their module maintained.
>
> > An ongoing program of testing existing modules against the current
> unstable Perl version would be a further improvement in quality
> control/assurance but I doubt we have the interest or manpower available to
> do it.
>
> I believe cpan already does automated test suite runs of several versions
> of perl on several OSes for modules - no need for us to duplicate that.
>
> > Enough discussion.  Let's make a decision and get on with it.
>
> --
> 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-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Package delivery without XCode

[Mark Anderson]

I agree. Sometimes even I use these methods instead of MacPorts, but I
usually try to get Macports to work as hard as I can. VLC is the one
offender that really doesn't want to build sometimes.

—Mark
___
Mark E. Anderson 

On Mon, May 18, 2015 at 8:04 PM, Ryan Schmidt 
wrote:

>
> On May 18, 2015, at 4:11 PM, Craig Treleaven wrote:
>
> > Right now, as I see it, MacPorts is pretty much geared to coders and
> sophisticated users (system/network administrators, etc).  There exists a
> wider group of folks who just want to run a specific application or two
> (say Darktable and Gimp, just for instance).  If such users could just
> install "Pallet-lite" and then be able to install any of a few dozen major
> open-source applications, that might be pretty popular.
>
> Most of the software in MacPorts is something you would use from the
> command line (e.g. ImageMagick), or something that is server software (e.g.
> Apache or PostgreSQL) or is a compiler or interpreter for a programming
> language (e.g. PHP or Node or GCC). Users of such software would hopefully
> be comfortable using MacPorts from the command line.
>
> There's no reason why users who aren't comfortable with the command line
> (the "wider group of folks" you mention) can't also use MacPorts. It should
> not be beyond anyone's capabilities to read and follow the MacPorts
> installation instructions, and to type a few commands into a terminal
> window to install the software they want. And those who prefer to use a
> MacPorts GUI have a few choices for that. Hopefully Pallet will be a viable
> option again sometime in the future when it's fixed up. I think there was
> even a recent proposal from someone to do that.
>
> Most GUI software designed for the Mac is already distributed in a
> ready-to-install way by those respective projects. Your two examples, Gimp
> and Darktable, already are, for example. For a lot of GUI software, e.g.
> VLC, it's simply a lot less bother to just use the binaries the developers
> provide rather than trying to use MacPorts to install it.
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #47685: tesseract @3.02.02_2: needs license

[Mark Anderson]

Whoops. Yeah, thanks for the fix.

—Mark
___
Mark E. Anderson 

On Wed, May 13, 2015 at 12:10 AM, MacPorts  wrote:

> #47685: tesseract @3.02.02_2: needs license
> +--
>   Reporter:  larryv@…   |  Owner:  emer@…
>   Type:  defect | Status:  closed
>   Priority:  Normal |  Milestone:
>  Component:  ports  |Version:  2.3.3
> Resolution:  fixed  |   Keywords:  haspatch
>   Port:  tesseract  |
> +--
> Changes (by larryv@…):
>
>  * status:  new => closed
>  * resolution:   => fixed
>
>
> Comment:
>
>  maintainer timeout, r136242
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for OS X
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: GSoC Project: Revitalizing Pallet

[Mark Anderson]

I love it. I agree with Ryan, I think a portfile Editor/IDE should be a
separate MacPorts.framework project from Pallet.

—Mark
___
Mark E. Anderson 

On Wed, May 6, 2015 at 8:40 PM, Ryan Schmidt 
wrote:

>
> On May 6, 2015, at 5:14 PM, Kyle Sammons wrote:
>
> > My name's Kyle Sammons and I've been accepted into this years GSoC. I
> was also a GSoC participant for MacPorts last year working on Project
> "Clean-up Stuff", which created the "port doctor" and "port reclaim"
> commands.
> >
> > My project for this year is to get Pallet, the MacPorts GUI, up and
> running with the support for newest versions of OS X and XCode. After that,
> I intend to give it, and the Framework, some more modern-day-MacPorts
> features. No features are set in stone as of yet, but I'm considering
> adding doctor, reclaim, rev-upgrade, a progress bar, or possibly even the
> ability to edit portfiles.
> >
> > Once again, none of these potential features are set in stone so if you
> guys would like to suggest any that would be nice to have, or have some
> questions/concerns about the project, feel free to shoot me an email.
>
> Great idea! I would only propose that you *not* pursue the idea of letting
> people edit portfiles, as that opens up lots of possibilities for problems.
> Pallet should be the utility for users who are not comfortable using the
> command line. Those users don't need to be editing portfiles.
>
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Death of Google Code

[Mark Anderson]

Yeah, I'm waiting to see what tesseract does. I'm hoping since its a google
project, it won't be abandoned. The upside is you can migrate any project
to github yourself. You don't have to own it.

—Mark
___
Mark E. Anderson 

On Fri, Mar 13, 2015 at 2:45 PM, Niels Dettenbach (Syndicat IT & Internet) <
n...@syndicat.com> wrote:

> Am 13. März 2015 19:03:56 MEZ, schrieb Ryan Schmidt <
> ryandes...@macports.org>:
> >We should still try to identify which ports are using a Google Code
> >project as their homepage or master_sites location, see if the projects
> >have already moved elsewhere, and, if so, update the ports. And if not,
> >see if the developer has plans to move. And if not, encourage them to
> >do so.
>
> I will do so for:
>
>  - MacPorts
>  - Gentoo ebuilds
>
> as soon as new official URIs are out ( beside http://darkice.org/download/
> mirror) - because i've maintained them in the past.
>
> Pls post it here as soon as available.
>
> many thanks,
>
>
> Niels.
> --
> Niels Dettenbach
> Syndicat IT & Internet
> http://www.syndicat.com
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Death of Google Code

[Mark Anderson]

Do we have any idea what we need to do/should do to prepare for the
eventual shutdown of google code? I know a lot of stuff has been abandoning
it, but I feel like we've got quite a few ports out there that will be hit.


—Mark
___
Mark E. Anderson 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #46844: help2man: add support for perl5.{16,18,20}

[Mark Anderson]

Yeah. I think bumping it to 5.20 is the best idea, as we slowly move toward
toward the goal of One Perl to Rule Them All. Or whatever we wind up doing.

—Mark
___
Mark E. Anderson 

On Sun, Feb 15, 2015 at 1:34 PM, Mojca Miklavec  wrote:

> On Sat, Feb 14, 2015 at 5:07 AM, Ryan Schmidt wrote:
> > I also wouldn't have a problem with individual ports like help2man
> moving to newer perl versions like 5.20. I don't feel that we need to wait
> and try to do every single port at once, as that's likely to either not
> happen because of the amount of work involved or to introduce problems
> because of insufficient testing.
>
> It would actually be really nice if someone would volunteer to create
> a new ticket like this one:
> http://trac.macports.org/ticket/44405
> to replace 5.16 with 5.20 and if we start the transition towards 5.20
> (optimally before they release 5.22).
>
> Being able to pick perl5_20 allows one to "get rid of" perl 5.16 and
> allows for some more testing, but if 5.20 is supported out of the box,
> there might be no need to offer the choice.
>
> I like variants, but I hate one specific aspect of them: when user
> installs one variant by default (for example +perl5_16) and when the
> default shifts to, say, +perl5_20, the user's choice remains at the
> old value (for no good reason) and the user no longer gets binary
> archives. I usually experience this "problem" with +gcc4x or +clang3x.
>
> Mojca
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: memberlist

[Mark Anderson]

I do like the idea of a forum or something. Gmail helps with conversation
management, but trying to find conversations from long ago, even with the
archive kinda sucks. Especially for those of us that have mail back when
this was "darwinports"

—Mark
___
Mark E. Anderson 

On Tue, Feb 10, 2015 at 6:08 PM, Brandon Allbery 
wrote:

> On Tue, Feb 10, 2015 at 6:02 PM, Ryan Schmidt 
> wrote:
>
>> As far as I know, Gmail is unique in that it deduplicates for you and
>> only shows you one copy. I assume it uses the Message-ID to do so.
>
>
> It's not unique; Cyrus imapd could be configured to do so in early
> versions and does it by default in 2.x and later. Since Zimbra started out
> as Cyrus, I imagine it does dedup by default as well.
>
> --
> brandon s allbery kf8nh   sine nomine
> associates
> allber...@gmail.com
> ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad
> http://sinenomine.net
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Looking for some advice on Google Code

[Mark Anderson]

Tesseract is moving it's files to Google Drive since Google Code no longer
allows uploads. Do we have a way to download from google drive? Should we?
Or should I just pull a tag from subversion?

—Mark
___
Mark E. Anderson 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

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 

On Sun, Jan 25, 2015 at 4:52 PM, Craig Treleaven 
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=assigned&status=
> new&status=reopened&port=~handbrake&order=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-us...@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #46004: perl5.18: update to 5.18.4

[Mark Anderson]

Cool. Totally slipped my mind.

—Mark
___
Mark E. Anderson 

On Tue, Dec 23, 2014 at 2:11 PM, MacPorts  wrote:

> #46004: perl5.18: update to 5.18.4
> ---+
>   Reporter:  mojca@…   |  Owner:  emer@…
>   Type:  update| Status:  closed
>   Priority:  Normal|  Milestone:
>  Component:  ports |Version:
> Resolution:  fixed |   Keywords:
>   Port:  perl5.18  |
> ---+
> Changes (by mojca@…):
>
>  * status:  new => closed
>  * resolution:   => fixed
>
>
> Comment:
>
>  Committed in r129941 as maintainer timeout.
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for OS X
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #43311: iTerm2: update to 1.0.0.20140403

[Mark Anderson]

I have a patch in this ticket to upgrade iTerm2 to v 2.0 - Should we change
the name of the ticket or start a new one?

—Mark
___
Mark E. Anderson 

On Sun, Oct 5, 2014 at 11:32 PM, MacPorts  wrote:

> #43311: iTerm2: update to 1.0.0.20140403
> -+--
>   Reporter:  nad@…   |  Owner:  emer@…
>   Type:  update  | Status:  new
>   Priority:  Normal  |  Milestone:
>  Component:  ports   |Version:  2.2.1
> Resolution:  |   Keywords:  haspatch
>   Port:  iTerm2  |
> -+--
>
> Comment (by emer@…):
>
>  Yeah, I have an incoming patch for that.
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for OS X
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: perl5.20

[Mark Anderson]

Yeah, I'm with Daniel here. I think we should only support the latest
version of Perl.

>From perl.org: "*We recommend that you always run the latest stable
version, currently 5.20.0"*

The whole reason we are in this mess is that long gap you see between 5.8
and 5.10 when we all thought Perl 6 was just around the corner (and always
will be). Now that we have a yearly release cadence we should just stick to
the latest.

5.205.20.02014-05-275.185.18.02013-05-185.165.16.02012-05-205.145.14.0
2011-05-145.125.12.02010-04-125.105.10.02007-12-185.85.8.02002-07-18


—Mark
___
Mark E. Anderson 


On Wed, Jul 23, 2014 at 6:48 PM, Daniel J. Luke  wrote:

> On Jul 23, 2014, at 6:26 PM, Frank Schima  wrote:
> >
> > As long as everything works in 5.20. So far I’m hitting a few bumps with
> p5.20-digest-sha1 [1] and p5.18-pdl not compiling. I can’t even try
> p5.20-pdl until p5.20-digest-sha1 is fixed.
>
> note that they both build find on a 'vanilla' install of perl5.20...
> --
> 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-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #41660: geda-gaf @1.6.2_0 (epoch 1): Update port to stable-1.8.2

[Mark Anderson]

Yeah, that's been on the backburner for me for a while. I have a path to
upgrade now, so I'll get on that.

—Mark
___
Mark E. Anderson 


On Fri, Jul 11, 2014 at 10:22 AM, MacPorts  wrote:

> #41660: geda-gaf @1.6.2_0 (epoch 1): Update port to stable-1.8.2
> ---+
>   Reporter:  trm70@…   |  Owner:  emer@…
>   Type:  update| Status:  new
>   Priority:  Normal|  Milestone:
>  Component:  ports |Version:
> Resolution:|   Keywords:
>   Port:  geda-gaf  |
> ---+
>
> Comment (by mojca@…):
>
>  This is not strictly related to the upgrade, but it's the only open ticket
>  about `geda-gaf`.
>
>  Version 1.6.2 from the buildbot somehow links against an outdated libpng.
>  I'll revbump the port for now, but here's the potential list of other
>  dependencies (some of them might not be relevant as I didn't rebuild ports
>  with `delete_la_files`):
>  {{{
>  atk
>  cairo
>  fontconfig
>  freetype
>  gdk-pixbuf2
>  geda-gaf
>  gettext
>  glib2
>  gmp
>  gtk2
>  guile
>  libiconv
>  libtool
>  pango
>  xorg-libX11
>  xorg-libXau
>  xorg-libXcomposite
>  xorg-libXcursor
>  xorg-libXdamage
>  xorg-libXdmcp
>  xorg-libXext
>  xorg-libXfixes
>  xorg-libXi
>  xorg-libXinerama
>  xorg-libXrandr
>  xorg-libxcb
>  xrender
>  }}}
>  When working on 1.8, you might want to revisit the dependencies (please
>  don't blindly use my list).
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for OS X
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: perl (again)

[Mark Anderson]

I sadly have not had enough time to work on cpan-mp, I've been mostly
learning the internals of macports first. But yeah, like I said on that
other thread, the latest perl is enough. Back when 5.x stalled because
everyone thought 6 was coming out it was ok to stay still. But now we get
new Perls regularly.

—Mark
___
Mark E. Anderson 


On Tue, Jun 10, 2014 at 7:42 PM, Mojca Miklavec  wrote:

> On Tue, Jun 10, 2014 at 8:37 PM, Daniel J. Luke wrote:
> > On Jun 10, 2014, at 2:21 PM, Mojca Miklavec wrote:
> >>
> >> I would be really grateful if someone would be
> >> willing to look into the above mentioned ticket. We would need a
> >> slight modification of the configure/build scripts.
> >
> > That change seems reasonable to me, but it would be worthwhile to look
> at what other packaging systems do (and/or to follow ryan's advice and talk
> to the perl devs about it)
>
> A while back I asked on stackoverflow and got a suggestion to install
> perlbrew.
>
> (
> http://stackoverflow.com/questions/23270656/how-to-install-perl-without-sub-version-number-in-path-lib-perl5-5-x-y-lib
> )
>
> But yes, we should ask that. (I nevertheless made a change in perl
> 5.20 to see how it works.)
>
> >> Other questions are still open. (One of the "complaints" about the
> >> current situation [ignoring the situation itself] is that if I go
> >> ahead and start modifying maintained p5-foo ports, maintainers will
> >> start complaining.
> >
> > I don't see that as a 'problem' (more works as intended) - you shouldn't
> make changes to a port someone else maintains without communicating with
> them (unless the port is 'broken').
>
> Yes, I understand that. But in the context of perl ports this *is* a
> problem. The only reasonable solution would be to open a ticket, CC
> all maintainers of all thousand perl packages, ask them to fix/upgrade
> their ports in the next 3-10 days (or argue why the ports shouldn't be
> changed), and that all other ports could be changed based on
> maintainer timeout at any time. Opening thousand tickets just to
> request an update seems like an overkill.
>
> (But yes, something needs to be done to facilitate automatic upgrades,
> at least for ports where no special treatment is needed.)
>
> > either we get the maintainers to update their ports, add openmaintainer,
> or we follow the port abandonment procedure and get the port updated to
> nomaintainer.
>
> Or that.
>
> > maybe eventually get some level 'automatic' support of modules from CPAN
> without having to write/update portfiles for each module when most of them
> will 'just work'?)
>
> Yes, that would be ideal. It just needs work.
>
> Btw: Perl 5.16 is no longer supported.
>
> Mojca
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #43480: perl: remove subrelease number from lib path

[Mark Anderson]

I (and I think Daniel Luke) just want to abolish all but the latest Perl.
We allow the installing of perls that have LONG since gone out of updates.
Perl goes out of its way to be backwards compatable. You have to do things
like "use 5.16" to even use new features that break stuff.

Mark

—Mark
___
Mark E. Anderson 


On Tue, Jun 10, 2014 at 7:34 PM, MacPorts  wrote:

> #43480: perl: remove subrelease number from lib path
> -+-
>   Reporter:  mojca@… |  Owner:  macports-
>   Type:  enhancement |  tickets@…
>   Priority:  Normal  | Status:  new
>  Component:  ports   |  Milestone:
> Resolution:  |Version:
>   Port:  perl5.8 perl5.10 perl5.12 perl5.14  |   Keywords:
>   perl5.16 perl5.18  |
> -+-
>
> Comment (by mojca@…):
>
>  I still agree that we probably want to talk to the developers, but I went
>  ahead and applied a patch r120890 to `perl5.20`. Given that the port is
>  completely new anyway, we won't break anyone's functionality and if the
>  idea turns out not to work ... well then we can revert it.
>
>  The problem with upstream is that they have a different model of
>  installing and using Perl than MacPorts does and I understand why for them
>  the model works and why they wouldn't want to switch to what I did, at
>  least not by default. One installs one version of perl and keeps it there
>  even after installing the next new version. But MacPorts removes the old
>  version (and doesn't provide experimental versions) and there's where the
>  problems start.
>
>  We need to make a strong case and request a new feature, so that they
>  would add a new configure option.
>
>  I would suggest to apply the same change also to `perl5.18`. (Or maybe
>  we'll change the way Perl works altogether anyway.)
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for OS X
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Noticing Perl stuff along the wire again

[Mark Anderson]

Love those ideas. Perl 6 is totally different so yeah, that'd be separate.
I'd like to see this expand to other package managers as well. pip, gems,
npm, and weird things that need supporting like rvm.

But Perl is my wheelhouse, so I'm starting there. Also, I think it needs
the most work right now.

Where would be a good place to stick this on the Wiki. There doesn't seem
to be a natural spot.

Mark

--Mark
___
Mark E. Anderson 


On Sat, Apr 5, 2014 at 9:20 AM, Brandon Allbery  wrote:

> On Sat, Apr 5, 2014 at 1:59 AM, Mojca Miklavec  wrote:
>
>> I also agree. (But maybe keep support for Perl 6 as a separate port(?) in
>> mind.)
>>
>
> Perl 6 is different enough that there's not much point in trying to fit it
> into this.
>
> --
> brandon s allbery kf8nh   sine nomine
> associates
> allber...@gmail.com
> ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad
> http://sinenomine.net
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Noticing Perl stuff along the wire again

[Mark Anderson]

I'm with you 100% there. Whatever we do it should be properly planned. Let
me dig though and put together a draft.

Mark

--Mark
___
Mark E. Anderson 


On Fri, Apr 4, 2014 at 7:08 PM, Joshua Root  wrote:

> On 2014-4-5 07:24 , Daniel J. Luke wrote:
> > On Apr 4, 2014, at 1:20 PM, Mark Anderson  wrote:
> >>
> >> I know we've argued about this time and time again, but Perl issues are
> coming back up it seems. I've started work - admittedly not getting very
> far on the cpan-mp idea. I'm still trying to figure out /base to be honest
> and brush off my Perl-XS skills.
> >
> > do you have anything where someone can look at it?
> >
> > I'd be interested in helping make things better...
> >
> >> I feel like we have had this argument again and again, and I'm loathe
> to start this argument again, but at what point are we going to pull the
> trigger on keeping one perl, deciding to drop old Perls, that kind of
> thing. I can put together a proposal and drop it on the wiki - if that will
> make things easier to decide/pick apart.
> >
> > A wiki page might be a good idea - it seems like there are a few people
> who are strongly opposed to that general plan (keeping just one good perl),
> and that there's been enough inertia to keep things from changing.
>
> I don't really care what we do with perl as long as it works. I've done
> way more work on the perl ports than I ever wanted to, simply because
> they were broken and stopping other stuff from working.
>
> There were some changes to perl begun in late 2008 that apparently
> weren't completely planned out and never really got finished. A lot of
> the subsequent work was attempting to fix that mess. So let's not have a
> repeat of that. Whatever we do, let's figure out where we're going
> before we start making changes, think through the impact on users and
> how to minimise it, and make the changes all at once when they're ready
> (ideally in a single commit).
>
> - Josh
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: git.macports.org not syncing since 11 March

[Mark Anderson]

Wow, yeah, that was a lot of stuff that came down.

Mark

--Mark
___
Mark E. Anderson 


On Fri, Apr 4, 2014 at 2:35 PM, Shreeraj Karulkar wrote:

> Finally git-push ran successfully. Can you please take a look and let me
> know if you see issues? Sorry for the delay.
>
> Shree
>
>
> On Apr 4, 2014, at 9:37 AM, Mark Anderson  wrote:
>
> Yeah, I continue to get "up-to-date" on my git pull upstream masters. I
> could have sworn more work was going on.
>
> Mark
>
> --Mark
> ___
> Mark E. Anderson 
>
>
> On Fri, Apr 4, 2014 at 3:51 AM, Rainer Müller  wrote:
>
>> On 2014-04-03 21:24, Shreeraj Karulkar wrote:
>> > I have changed it. THanks for brining this up.
>>
>> Hm, but the git mirror is still not updating. The latest commit synced
>> was r117767 on March 11.
>>
>> Rainer
>> ___
>> macports-dev mailing list
>> macports-dev@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
>>
>
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Noticing Perl stuff along the wire again

[Mark Anderson]

I know we've argued about this time and time again, but Perl issues are
coming back up it seems. I've started work - admittedly not getting very
far on the cpan-mp idea. I'm still trying to figure out /base to be honest
and brush off my Perl-XS skills.

I feel like we have had this argument again and again, and I'm loathe to
start this argument again, but at what point are we going to pull the
trigger on keeping one perl, deciding to drop old Perls, that kind of
thing. I can put together a proposal and drop it on the wiki - if that will
make things easier to decide/pick apart.


--Mark
___
Mark E. Anderson 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: MacPorts Developer Meeting?

[Mark Anderson]

If I can get myself to Europe. Depends on where and when.

--Mark
___
Mark E. Anderson 


On Fri, Apr 4, 2014 at 12:43 PM, Mojca Miklavec  wrote:

> Hi,
>
> I'm curious how many people would be willing and able to join if we
> organized a 3-5 day long developer meeting somewhere "in the heart of
> Europe" (somewhere close to public transportation, but outside of city
> centers, somewhere in nature).
>
> Let's assume that we could reach a price of 100 EUR (let's say 30
> EUR/day) with all costs included (that is: lodging, food, conference
> room rental, so you would only need to cover travel expenses in
> addition to that).
>
> This means:
> - finding a time slot when most people would be able to attend
> - making a reservation at some inexpensive holiday site
> - make sure they have good internet connection and a room with enough
> tables and chairs
> - collect reservations, prepare a (flexible) program
> - bring yourself and your mac to the site
> (- and maybe finding a sponsor to give us access to a high speed multi
> core mac during those few days to be able to compile things faster ;)
>
> The meeting would cover:
> - getting to know each other
> - some talks about amazing things you did, would like to do or would
> like to see done
> - brainstorming, round table with discussion about new ideas and future
> - hacking sessions, ticket closing marathon
> - enough free time to enjoy nature: walks or maybe some field trips around
>
> If we could get some 10-20 people to attend (and at least someone from
> "portmgr"), it could be an amazing experience.
>
> Any interest? (I'm thinking about 2015.)
>
> Mojca
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: git.macports.org not syncing since 11 March

[Mark Anderson]

Yeah, I continue to get "up-to-date" on my git pull upstream masters. I
could have sworn more work was going on.

Mark

--Mark
___
Mark E. Anderson 


On Fri, Apr 4, 2014 at 3:51 AM, Rainer Müller  wrote:

> On 2014-04-03 21:24, Shreeraj Karulkar wrote:
> > I have changed it. THanks for brining this up.
>
> Hm, but the git mirror is still not updating. The latest commit synced
> was r117767 on March 11.
>
> Rainer
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Move part of macports infrastructure to GitHub

[Mark Anderson]

sync certainly works with git as well.

--Mark
___
Mark E. Anderson 


On Thu, Mar 20, 2014 at 7:19 PM, Ryan Schmidt wrote:

>
> On Mar 20, 2014, at 02:46, Mojca Miklavec wrote:
>
> > Despite the fact that I kept pushing a couple of other projects to
> > switch to a different version control system (mostly from CVS to git),
> > MacPorts is one of those projects where the current system (trac with
> > nice linking between tickets and commits, subversion, buildbots, email
> > accounts, ...) works pretty well and also looks nice. I do miss some
> > functionality (like a website with a nice overview of packages with
> > their build success, latest few commits etc.), but that isn't
> > something that a migration can solve.
>
> Right, that's something improving the MacPorts web site should solve.
>
>
> > Subversion actually has a bunch of benefits over git in this
> > particular environment. Git is strong in merging, cherry-picking,
> > having a large number of branches etc., but I don't see much need for
> > that for maintaining Portfiles. The biggest problem with Portfiles is
> > that a number of people without commit rights might need to wait for a
> > long time before someone picks up their patch and commits it, but
> > switching to a different system would still mean that someone would
> > need to look at commit and test it before accepting it. The only thing
> > that could be different is probably a clearly visible pull request. In
> > MacPorts' trac it's not too easy to spot the difference between
> > "please commit this, it's fully functional" vs. "I've been just
> > playing around and tossing ideas - feel free to look and this patch
> > and improve it" vs. plain requests to fix things. And if a random
> > developer just happens to have time and is willing to test and commit
> > something, it's not clear in which of the thousands of open tickets to
> > start looking. (Trac searches and browsing through tickets based on
> > specific criteria could be improved, but I'm not sure how.)
>
> Such a person should search for tickets with the "haspatch" keyword; that
> keyword should probably only be used for patches that are ready to go.
>
>
> https://trac.macports.org/query?status=!closed&keywords=~haspatch&desc=1&order=id
>
>
> > That said, a git/hg mirror on GitHub/ButBucket would definitely be
> > nice.
>
> Why would that be nicer than the read-only git mirror that Mac OS Forge
> already provides here:
>
> http://www.macosforge.org/post/git-mirrors/
>
>
> > MacPorts could potentially offer a "selfupdate" from an
> > arbitrary git/hg repository clone if necessary (but one can already
> > have a clone on the filesystem and use that one).
>
> selfupdate uses rsync only.
>
> sync can use rsync or svn, possibly other version control systems already,
> I don't remember.
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Move part of macports infrastructure to GitHub

[Mark Anderson]

I'm mostly interested in being able to authenticate, add, and read tickets.
I'm looking to see if I can create a draft ticket from within my git
workflow.

--Mark
___
Mark E. Anderson 


On Tue, Mar 18, 2014 at 10:55 PM, Jeremy Lavergne <
jer...@lavergne.gotdns.org> wrote:

> Google shows there are plugins available.
>
> Is there somethign specific you're interested in seeing?
>
> On Mar 18, 2014, at 22:15, Mark Anderson  wrote:
>
> > Does our install of Trac have any public APIs (XMLRPC, REST, SOAP,
> whatever)?
> >
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Move part of macports infrastructure to GitHub

[Mark Anderson]

Related side question:
Does our install of Trac have any public APIs (XMLRPC, REST, SOAP,
whatever)?

Mark



--Mark
___
Mark E. Anderson 


On Tue, Mar 18, 2014 at 3:51 PM, Landon Fuller  wrote:

>
> On Mar 16, 2014, at 11:40 PM, Joshua Root  wrote:
>
> However I would also agree with what Landon said here:
> <
> https://lists.macosforge.org/pipermail/macports-dev/2013-September/024252.html
> >
>
>
> I'm glad I read the full thread, as otherwise I might have reiterated this
> point without realizing I'd already made it :-)
>
> That said --
>
> The better I understand git, the less I like it, but the fact is that the
> industry has shifted and git is the leader *for now*. I'd certainly
> support a move to git, especially if we had the time and server-side
> control necessary to disable dangerous, data-destroying features such as
> permanent deletion of branches+tags and forced pushes, and thus could be
> assured that repository history would remain correct and internally
> consistent until the *next* SCM emerges.
>
> However, I still think it's a backwards step to abandon self-hosted
> control of critical project infrastructure, and I don't think there's a
> compelling technical or administrative argument for Github that outweighs
> this. I've not seen *better* or more *correct* contributions by using
> Github on projects; rather, it seems to lower the bar (and even that is
> arguable) on the least important part of the process -- submitting the patch.
>
> I also have some ethical qualms about contributing to the furtherance of
> what amounts to Github's social network lock-in through network effects.
> They're a commercial organization, and I don't think an open source
> monoculture defined and driven by GitHub's business goals and ideals of how
> people should manage projects is to open source's benefit.
>
> Lastly, I question the wisdom of tying a project that has already lived
> for 12 years to a commercial "SaaS" offering. Recently, I had to move some
> small projects off of Google Code -- because Google had deprecated and
> removed their data APIs, I had to actually use a screen scraper to
> (lossily) export my Google Code issues.
>
> If you'd told me 8 years ago that Google would pull the data APIs and make
> it difficult to leave, I wouldn't have believed it.
>
> -landonf
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Move part of macports infrastructure to GitHub

[Mark Anderson]

Ok. I'm willing to play ball on that. Also since Atlassian products are
pretty cool. I just like the idea of a more modern workflow. If I got a
vote, which I suppose I don't, It would be git/github, but hg/bitbucket is
ok. Git/bitbucket is what I use on the side as well.

--Mark
___
Mark E. Anderson 


On Sun, Mar 16, 2014 at 3:31 PM, Sean Farley  wrote:

>
> Ryan Schmidt  writes:
>
> > On Mar 16, 2014, at 13:27, Ivan Larionov wrote:
> >
> >> I want to start this discussion mainly about ports tree, but actually
> base and some other stuff could use github and infra around it as well. I
> understand this is not so easy and may be you already discussed it and may
> be already decided not to do, but there are huge pros:
> >>
> >> * git >> svn
> >
> > For you, moving from svn to git may be a pro; for me, it would initially
> be a con. I have a decade of experience with Subversion and a very good
> understanding of how it works and behaves, and only an extremely spotty
> understanding of git. It makes me uncomfortable every time I use it. That
> could be cured by spending some hours with a fine manual, but it would be
> something new to need to learn. Although I understand github does offer svn
> access to its git repositories, so it's possible those like me who would
> prefer not to be forced to switch to git wouldn't have to.
>
> Coming from years of supporting projects moving from Subversion to git /
> Mercurial, it has been my experience that Mercurial has a much more sane
> user interface and doesn't force the user to grok the internals as I've
> found git does.
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Move part of macports infrastructure to GitHub

[Mark Anderson]

Yeah, I agree with Ivan, the big deal is Github. Git is great, but hg
offers a lot of the same stuff. As to Ryan's objections, I too had those
same objections after working with SVN and CVS for almost 2 decades. But
once I switched, I wondered why I hadn't switched earlier. I'm sure those
of us in the community would be more than happy to help move things over, I
know I would. I've been wanting to get more and more involved for a while.
And I know Github pretty well. I also use Github Enterprise at work.

Not for nothing, but that search turned up roughly 22 pages of personal
Macports repos. (alhtough a few referenced "Macports sucks" which I don't
like, but eh. It was more positive than negative.

Mark





—Mark
___
Mark E. Anderson 


On Sun, Mar 16, 2014 at 3:13 PM, Ivan Larionov wrote:

> Actually main thing here isn’t git, but github. It’s interface and features
> take contribution process to the next level. It’s so easy — just fork,
> commit
> and send pull request.
>
> I understand that someone could like mercurial more and we have bitbucket,
> but actually, I see people use github more and like it.
>
> --
> With best regards, Ivan Larionov.
>
> On 16 марта 2014 г., at 22:42, Sean Farley  wrote:
>
>
> Ivan Larionov  writes:
>
> I want to start this discussion mainly about ports tree, but actually base
> and some other stuff could use github and infra around it as well. I
> understand this is not so easy and may be you already discussed it and may
> be already decided not to do, but there are huge pros:
>
> * git >> svn
> * pull requests are awesome! No need to poke around with patch files
> attached to tickets
> * nice UI, tools and infra around
>
> which will result in more pros:
>
> * people will look at macports more positively
> * and will contribute more!
>
> Actually I see lot of people keeping their local ports at github:
> https://github.com/search?q=macports&type=Repositories&ref=searchresults
>
> What do you think?
>
>
> I know this is a hot topic but I will try to avoid any flame wars.
>
> If MacPorts really wants to switch to distributed version control, then
> I would suggest Mercurial. I have experimented with using Mercurial for
> the MacPorts repo and found that the mercurial UI is much, much more
> consistent than git coming from Subversion.
>
> I've actually maintained a repo with merges, tags, and branches
> correctly merged in here:
>
> https://smf.io/macports
>
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Move part of macports infrastructure to GitHub

[Mark Anderson]

Yeah, I actually like the idea of GitHub for the idea of pull requests. So
much so, I mirror the Macports on github, make my changes in branches and
make patches for SVN there. I'm certain we could save all the history we
needed. I've made this shift several times on a few projects.

I even have base in there, where I am working on my Perl CPAN runner
(another hot topic, I know), so we maybe won't need 87 Perls.

--Mark
___
Mark E. Anderson 


On Sun, Mar 16, 2014 at 2:52 PM,  wrote:

> On 16 Mar 2014, at 19:42 , Sean Farley  wrote:
> > I would suggest Mercurial.
>
> +1
>
> But, in order to avoid any flamewars: I'd be going for git as well, if it
> would win in an election. :-)
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Restarting Perl Arguments. :-P

[Mark Anderson]

Yep. Right now that's just the pure (perhaps a few commits back) repo as
all my changes of late have made it into trunk.

Mark

--Mark
___
Mark E. Anderson 


On Sun, Feb 9, 2014 at 10:09 PM, Arno Hautala  wrote:

> I'm guessing it will be here: https://github.com/markemer/Macports
>
> On Sun, Feb 9, 2014 at 5:27 PM, Eric Gallager 
> wrote:
> > Do you have a link to your fork on Github? I would like to "star" it.
> >
> >
> >
> > On Sun, Feb 9, 2014 at 2:52 PM, Mark Anderson  wrote:
> >>
> >> So I've started messing around with getting a Proof of Concept CPAN->MP
> >> link working, so we don't need to have to have 8 billion perl ports.
> This
> >> was an idea on a thread long ago. I'll be keeping a github branch in my
> fork
> >> as soon as I get something that resembles something that isn't "how in
> the
> >> hell does this work" jibberish.
> >>
> >> Anyone who's interested, give me a holler, and I'll keep you in the
> loop.
> >>
> >> --Mark
> >> ___
> >> Mark E. Anderson 
> >>
> >> ___
> >> macports-dev mailing list
> >> macports-dev@lists.macosforge.org
> >> https://lists.macosforge.org/mailman/listinfo/macports-dev
> >>
> >
> >
> > ___
> > macports-dev mailing list
> > macports-dev@lists.macosforge.org
> > https://lists.macosforge.org/mailman/listinfo/macports-dev
> >
>
>
>
> --
> arno  s  hautala/-|   a...@alum.wpi.edu
>
> pgp b2c9d448
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Restarting Perl Arguments. :-P

[Mark Anderson]

So I've started messing around with getting a Proof of Concept CPAN->MP
link working, so we don't need to have to have 8 billion perl ports. This
was an idea on a thread long ago. I'll be keeping a github branch in my
fork as soon as I get something that resembles something that isn't "how in
the hell does this work" jibberish.

Anyone who's interested, give me a holler, and I'll keep you in the loop.

--Mark
___
Mark E. Anderson 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: changing default perl

[Mark Anderson]

Well, I don't really care, but I'm not sure if this is changed, but with
python I see a lot of variants that let me pick the python to support
rather than just pick say +perl. Because there is a lot of just +perl out
there, I get into a mix and match problem.

For example: GraphViz is against perl5.14, Subversion is against perl5.16
and thus I can't use them together. It's the bindings that I really care
about. I'm pulling that out of thin air right now, but I have run into this
problem more than once.

—Mark
___
Mark E. Anderson 


On Sun, Nov 3, 2013 at 5:11 PM, Ryan Schmidt wrote:

>
> On Nov 3, 2013, at 16:07, Mark Anderson wrote:
>
> > I like the idea of a port select like python, which as worked well for
> me. With python, in most cases, I can just keep the most current 2.x and
> most current 3.x. I'm not sure if python just works better, and we need to
> mirror that approach, or there is something else at play.
>
> perl5 currently does mirror the python and php approaches, more or less,
> with the exception that we didn’t have “port select” when the current perl5
> ports were designed, so we don’t have that yet.
>
>
> > What really drives me crazy is that Macports continually insists on
> installing perl 5.12 which is 3+ years old. If there were specific port
> related reasons, I would be less upset, but in most cases, I can uninstall
> or stop the perl5.12 install, changed the dependence in the portfile to
> 5.18 locally and everything works just fine.
>
> Why does it matter what ports MacPorts installs for its own purposes? It
> doesn’t prevent you from installing whatever ports you want for your
> purposes. Do you also complain when MacPorts installs autoconf or gettext
> just because you don’t personally need to use those ports directly?
>
>
> > I lean toward a port select idea, where we can limited the number of
> installed Perls to ones we want or have a real need to keep. Perl should
> play nice with other installed Perls, so I'm not against offering a few
> versions back and maybe the latest current unstable odd numbered perl like
> 5.19. At this point we can probably ditch perl 5.8 and maybe 5.10 to make
> things easier.
>
> Remember that “port select” is for your convenience as a user. Ports
> should not use what you have selected. Ports should continue to declare
> dependencies on the specific ports they need.
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Fwd: changing default perl

[Mark Anderson]

+ Macports-dev

-- Forwarded message --
From: Mark Anderson 
Date: Sun, Nov 3, 2013 at 5:07 PM
Subject: Re: changing default perl
To: Ryan Schmidt 


I like the idea of a port select like python, which as worked well for me.
With python, in most cases, I can just keep the most current 2.x and most
current 3.x. I'm not sure if python just works better, and we need to
mirror that approach, or there is something else at play.

What really drives me crazy is that Macports continually insists on
installing perl 5.12 which is 3+ years old. If there were specific port
related reasons, I would be less upset, but in most cases, I can uninstall
or stop the perl5.12 install, changed the dependence in the portfile to
5.18 locally and everything works just fine.

I lean toward a port select idea, where we can limited the number of
installed Perls to ones we want or have a real need to keep. Perl should
play nice with other installed Perls, so I'm not against offering a few
versions back and maybe the latest current unstable odd numbered perl like
5.19. At this point we can probably ditch perl 5.8 and maybe 5.10 to make
things easier.

—Mark
___
Mark E. Anderson 


On Sun, Nov 3, 2013 at 4:42 PM, Ryan Schmidt 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?
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Maverics/Xcode 5 proposal: no more xcode-select --install

[Mark Anderson]

Will xcode-select --install work right without XCode.app? I do OSX and Mac
Dev, so I always have it, but I'm curious to try now.

—Mark
___
Mark E. Anderson 


On Wed, Oct 30, 2013 at 7:52 PM, Ned Deily  wrote:

> In article ,
>  Paul Bennett  wrote:
>
> > On 30 Oct 2013, at 23:04, Ned Deily  wrote:
> > > In article <52711f90.70...@macports.org>,
> > > Rainer Muller  wrote:
> > >> Well, after thinking about this again, we could also do it the other
> way
> > >> around. The majority of ports already builds just fine if you have the
> > >> Command Line Tools only, without Xcode (ignore warnings from base
> about
> > >> missing xcodebuild, it's not actually required in this case).
> > [...]
> > > From the outside looking in, that strikes me as a much more realistic
> and
> > > potentially achievable goal.
> >
> > I'd still like to encourage considering both cases:
> > 1. When Xcode is installed, but Command Line Tools aren't
> > 2. When Command Line Tools are installed, but Xcode isn't
> >
> > From my position, I don't see that the scale of 2 is significantly
> different
> > to 1, particularly since in both cases the shims - including xcrun -
> will be
> > there to assist locating the relevant tools, headers and libraries.
>
> The problem I see with proposal one is that there are plenty of upstream
> projects that make assumptions about file locations, like header file
> locations, and were never designed to take into account the use of an an
> SDK.
> The Apple compiler drivers handle the cases involving compiler and linker
> calls, e.g. through the use of -isdkroot and the under-the-covers appending
> the SDK prefix to paths to "system" locations, but that doesn't and can't
> help
> with paths that are embedded or, worse, computed dynamically elsewhere in a
> project's build steps.  For example, python builds use a python script for
> the
> steps of building the C extension modules in its standard library.  At
> build
> time, the script does a lot of searching around to find include files and
> library files to determine which extensions to build and/or how to build
> them.
> To support SDK builds, we (the Python project) had to go in and modify
> setup.py to do the SDK path modifications itself and sometimes we slip up.
>  In
> the best case, that produces a build error; in other cases, it hasn't but
> created a component with subtle bugs.  I'm sure there are plenty of other
> cases in other projects.  The problem is that it's impossible to identify
> all
> of these uses automatically.  And even if you catch some of them and send
> the
> changes back upstream (and if you don't, you've just added an on-going
> maintenance headache), there still is no guarantee that you've caught most
> of
> them.
>
> Proposal two is much easier because that's how projects are built on most
> other Unix-y platforms.  Only OS X specific ones and ones where, for some
> reason, the upstream project came up with an xcode project file would you
> really need to have Xcode.app installed.
>
> --
>  Ned Deily,
>  n...@acm.org
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Status of Macports_Framework

[Mark Anderson]

I figured out what I did. The link in the wiki points to the wrong spot.
I'll go fix that when I have a chance. I knew I had built something much
more recent than 6 years ago last time I built Pallet. Thanks everybody.

—Mark
___
Mark E. Anderson 


On Tue, Oct 29, 2013 at 6:50 AM, Rainer Müller  wrote:

> On 2013-10-29 04:54, Joshua Root wrote:
> > On 2013-10-29 14:36 , Mark Anderson wrote:
> >> What's the status of Macports_Framework? I was looking in SVN and the
> >> last commit was 6 years ago. I was looking to work on it, is that the
> >> latest?
> >
> > I haven't tried it lately, but there have definitely been commits more
> > recently than that, r102779 being the last.
>
> As far as I know, all the work from GSoC 2009 and GSoC 2010 have been
> merged back into the contrib directory.
>
> Rainer
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Status of Macports_Framework

[Mark Anderson]

Ok, thanks, I thought their had to be. I must be looking in the wrong spot.

—Mark
___
Mark E. Anderson 


On Mon, Oct 28, 2013 at 11:54 PM, Joshua Root  wrote:

> On 2013-10-29 14:36 , Mark Anderson wrote:
> > What's the status of Macports_Framework? I was looking in SVN and the
> > last commit was 6 years ago. I was looking to work on it, is that the
> > latest?
>
> I haven't tried it lately, but there have definitely been commits more
> recently than that, r102779 being the last.
>
> - Josh
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Status of Macports_Framework

[Mark Anderson]

What's the status of Macports_Framework? I was looking in SVN and the last
commit was 6 years ago. I was looking to work on it, is that the latest?

—Mark
___
Mark E. Anderson 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #40654: Upgrade of iterm2

[Mark Anderson]

Ok, so I just needed to RTFM, I had a feeling. Thanks!

Mark

—Mark
___
Mark E. Anderson 


On Wed, Oct 2, 2013 at 7:38 PM, Craig Treleaven wrote:

> At 7:30 PM -0400 10/2/13, Mark Anderson wrote:
>
>> I submitted two tickets 40653 and 40654 with patches, that are
>> nomaintainer. I would be willing to take them over, but I wasn't sure how I
>> was supposed to do that. Just declare myself the maintainer? I also
>> contributed a perl 5.18 Portfile, which seems to have a maintainer +
>> openmaintainer. I'd wasn't sure how that worked either. Can someone tell me
>> how this works or where I need to RTFM?
>>
>
> I don't have commit privs but I maintain a couple ports.  Info at:
>
> http://guide.macports.org/#**project.contributing<http://guide.macports.org/#project.contributing>
>
> Craig
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #40654: Upgrade of iterm2

[Mark Anderson]

I submitted two tickets 40653 and 40654 with patches, that are
nomaintainer. I would be willing to take them over, but I wasn't sure how I
was supposed to do that. Just declare myself the maintainer? I also
contributed a perl 5.18 Portfile, which seems to have a maintainer +
openmaintainer. I'd wasn't sure how that worked either. Can someone tell me
how this works or where I need to RTFM?

Thanks,
Mark

—Mark
___
Mark E. Anderson 


On Wed, Oct 2, 2013 at 7:23 PM, MacPorts  wrote:

> #40654: Upgrade of iterm2
> +
>  Reporter:  emer@…  |  Owner:  macports-tickets@…
>  Type:  update  | Status:  new
>  Priority:  Normal  |  Milestone:  MacPorts Future
> Component:  ports   |Version:  2.2.99
>  Keywords:  |   Port:  iterm2
> +
>  Upgrade of iterm2 to latest version.
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for OS X
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Perl 5.18

[Mark Anderson]

Oh ok. Thanks. That's the kind of thing I was wondering about.

—Mark
___
Mark E. Anderson 


On Mon, Sep 23, 2013 at 6:45 PM, Ryan Schmidt wrote:

> On Sep 23, 2013, at 17:01, Mark Anderson wrote:
>
> > Here is my more important question: What other things need to be done to
> bring up a new perl? I know perl5 needs to be modified, but there have to
> be other things like Portgroups or something.
>
> Any perl module ports that want to offer perl 5.18 subports need to so
> indicate in their perl5.branches line. This cannot be done in a portgroup;
> it must be done individually in every port, because every port must take
> individual responsibility for being perl 5.18 compatible.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Perl 5.18

[Mark Anderson]

I've managed to get Perl 5.18 to compile and run. I'm wondering, has anyone
started the effort for a perl 5.18.1 port? If not, I'll open a ticket and
start prettying up my port.

Here is my more important question: What other things need to be done to
bring up a new perl? I know perl5 needs to be modified, but there have to
be other things like Portgroups or something.

Thanks,
—Mark
___
Mark E. Anderson 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [110471] trunk/dports/aqua/qt4-mac/Portfile

[Mark Anderson]

I have access, and I can't really discuss problems here because of the
strict NDA. I've been trying to find solutions, but I'm on my own. That
said, a lot of changes will need to be made for Mavericks, but that's
nothing new. Every update is like this.

Mark

—Mark
___
Mark E. Anderson 


On Sat, Aug 31, 2013 at 3:00 PM, Jeremy Lavergne  wrote:

> If this were actually a concern for Apple they would address it.
>
> On Aug 31, 2013, at 2:36 PM, Ryan Schmidt wrote:
>
> >> Do we, as MacPorts developers, get any access to Mavericks before it
> comes out so that we can work on fixing issues such as this?
> >
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apple's bug reporter

[Mark Anderson]

Doh. Perhaps it works better pre-release. I certainly recommend people on
Mavericks to report early and often.

Mark

—Mark
___
Mark E. Anderson 


On Thu, Jul 11, 2013 at 7:21 PM, Mojca Miklavec  wrote:

> On Fri, Jul 12, 2013 at 1:05 AM, Mark Anderson wrote:
> > Oh, I filed reports with apple. In fact, for anyone with troubles on any
> > OSX, http://bugreporter.apple.com is your best friend. Use it.
>
> Not that I want to discourage anyone, but not any single bug that I
> ever reported (I probably reported the first one around 2007) has ever
> been fixed.
>
> For one particular bug I remember experiencing it on Tiger (my first
> OS X ever), Leopard was consistently crashing on the same file (just
> trying to upload a simple regular valid PDF file made any web browser
> crash), Preview was nicely crashing too. With Snow Leopard it stopped
> crashing (most probably a matter of pure luck/by accident), but it
> still displayed the file horribly wrong. When I was already on Lion
> they decided to write back asking if the issue was resolved with the
> new OS. After replying that it wasn't, I never heard back.
>
> Even when printing was horribly broken (completely nonfunctional for
> Type1-flavoured OpenType fonts) and the bug must have influenced many
> printing businesses on macs, it took them a whole month to release a
> fix. I was begging friends to print files for me from Windows.
>
> Well, hope dies last. So filing a bug report from time to time might
> help the soul feel better ;)
>
> Mojca
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Macports Tcl

[Mark Anderson]

Oh, I filed reports with apple. In fact, for anyone with troubles on any
OSX, http://bugreporter.apple.com is your best friend. Use it.

It just made me think of the idea of reducing dependencies. Especially if,
for example, we want to move to Tcl 8.X or a new cURL/Subversion, before
Apple does.

I think a good start is what Ryan suggested. Start to bundle tcl 8.5 with
MacPorts and then move it to 8.6 unrelated to what Apple does.

Mark

—Mark
___
Mark E. Anderson 


On Thu, Jul 11, 2013 at 7:01 AM, Rainer Müller  wrote:

> On 2013-07-07 20:51, Mark Anderson wrote:
> > Mainly because of my troubles with a certain OSX that is not to be named
> > or the fiery NDA demons will smite me.
>
> There are ways to communicate such problems to Apple for those who have
> such troubles. The common measure seems to be the more reports they get,
> the more important is the issue. I encourage everyone to use these
> possibilities. The simplest solution for MacPorts would be that the
> target operating system ships a complete Tcl distribution that can
> actually be used for development.
>
> Rainer
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Switching to Perl 5.16

[Mark Anderson]

Yeah, this perl situation drives me crazy. I always wind up accidentally
installing 5.12 when I don't want to, and I still have yet to install 5.18,
although I am looking at how to build that. I'm with Daniel. We should just
keep the latest stable(5.18) and p5-* and keep the perl5-XXs around if you
need to install an old one for some reason, but not linked to /usr/bin/perl

Mark

—Mark
___
Mark E. Anderson 


On Mon, Jul 8, 2013 at 10:48 AM, Daniel J. Luke  wrote:

> On Jul 8, 2013, at 10:44 AM, Jeremy Huddleston Sequoia 
> wrote:
> >> do you have a reason why? We generally follow the upstream 'stable'
> release unless we've got a specific reason not to...
> >
> > Well that wasn’t the case while 5.14 was stable upstream nor while 5.16
> was stable upstream.
>
> and in both cases we were behind for no real reason (as far as I could
> tell at the time).
>
> > 5.18 doesn’t even exist in MacPorts yet.  Possibly by the time it
> becomes available, 5.20 will be out, and we’ll be having this same argument.
>
>
> only if we don't just jump to the current stable ;-)
> --
> 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-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Macports Tcl

[Mark Anderson]

I think that's what we're getting at. I may have been imprecise in how I
described it. I think we should have sone method to download and build some
of the tools we need and set them aside.

Mark



On Monday, July 8, 2013, Clemens Lang wrote:

> Hi,
>
> On Mon, Jul 08, 2013 at 07:19:38PM -0400, Mark Anderson wrote:
> > I kind of like the idea Ryan was talking about where we build using a
> > portfile or something, and then squirrel the files away someplace away
> > from the main install.
>
> So we have to create a script that will relocate an installed Tcl 8.6
> port into a new directory (e.g. /opt/local/lib/macports/Tcl)? Which
> variants of the tcl port that we currently have will work for this? What
> happens if a user installs a different variant? How do we solve the
> bootstrapping problem for users who want to build from source? Should we
> use a framework build of Tcl or not? How do we handle changes in the Tcl
> port? Re-run this step on every selfupdate?
>
> I think it might be easier to write a script that will download and
> install a proper Tcl version completely separate from MacPorts and call
> ./configure --with-tcl.
>
> --
> Clemens Lang
>
>

-- 
Sent from Gmail Mobile on iPhone
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Macports Tcl

[Mark Anderson]

Yeah, I've actually currently built against the MacPorts Tcl. I don't
recommend it, but it was the easiest way to rebuild between developer
seeds. I kind of like the idea Ryan was talking about where we build using
a portfile or something, and then squirrel the files away someplace away
from the main install.

—Mark
___
Mark E. Anderson 


On Mon, Jul 8, 2013 at 2:32 PM, Daniel J. Luke  wrote:

> On Jul 7, 2013, at 11:00 PM, Ryan Schmidt  wrote:
> > In fact, just naively making MacPorts base link with libraries provided
> by MacPorts ports would be brittle and unwise, e.g. if MacPorts base used a
> library from MacPorts cURL, and the user deactivated MacPorts cURL, then
> MacPorts wouldn't be able to use cURL anymore. But as I said it's possibly
> worth looking into ways of solving it.
>
>
> indeed, back a /long/ time ago I had built MacPorts against MacPorts
> provided tcl and then forgotten and uninstalled MacPorts tcl (it was an
> interesting situation to recover from) ;-)
>
> --
> 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-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Macports Tcl

[Mark Anderson]

Yeah. That was why I sort of just floated it as an idea. Mainly because of
my troubles with a certain OSX that is not to be named or the fiery NDA
demons will smite me.

And now that you mentioned curl and subversion it's making more sense to
me, since Macports likes to rely our own stuff to maximize compatibility.

Well, since I opened my big fat mouth, I'll take a look and put together
some ideas, see what everyone thinks. I knew I wasn't going to be able to
stay out of /base forever. :-P


—Mark
___
Mark E. Anderson 


On Sun, Jul 7, 2013 at 2:56 AM, Ryan Schmidt wrote:

> On Jul 6, 2013, at 17:50, Mark Anderson wrote:
>
> > I'm starting to wonder if we should include a bootstrapping version of
> Tcl with Macports, in case some future version of OSX ships with a broken
> version. Any thoughts?
>
> Yes, that topic recently came up. Someone pointed out that Tcl 8.6 offers
> improvements that would allow us to simplify or streamline some currently
> convoluted code in base.
>
> There have been buggy versions of Tcl shipped with OS X in the past. For
> example Tcl 8.5 in Leopard has a bug where unsetting environment variables
> doesn't work, which caused an endless variety of errors that were very
> difficult to track down and which therefore took months for someone to
> realize what was happening. MacPorts base currently includes code to work
> around that problem.
>
> We also currently use the system versions of cURL and Subversion, which on
> older OS X versions are missing some features.
>
> MacPorts currently does not ship with any libraries. If we wanted to
> change that, we would have to think about how to do that.
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Macports Tcl

[Mark Anderson]

I'm starting to wonder if we should include a bootstrapping version of Tcl
with Macports, in case some future version of OSX ships with a broken
version. Any thoughts?


—Mark
___
Mark E. Anderson 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: problem with MacPorts under Mavericks/Xcode5

[Mark Anderson]

I have a short term workaround to anyone who is also under the NDA.
I'm trying to come up with a long term solution. Email me if you are
in the Mac Developer Program and would like that info. I'm certain I
can't post it publicly here. We should probably set up a MacPorts-dev
discussion topic over in the NDA cleared apple forums for those of us
in it.

Mark
—Mark
___
Mark E. Anderson 


On Wed, Jun 12, 2013 at 3:06 AM, Artemio González López
 wrote:
>
> On 12 Jun 2013, at 07:07, Jeremy Huddleston Sequoia 
> wrote:
>
> 1) You are under NDA.
>
> 2) Use trunk.
>
>
> Thanks a lot for your help. I tried installing from trunk (with svn), but in
> the configure phase I got the following error message:
>
> checking for Tcl configuration... configure: error: Can't find Tcl
> configuration definitions
>
> Any suggestions?
>
> Thanks a lot again, and sorry for my clumsiness,
>
> Artemio
>
> Artemio Gonzalez Lopez
> artem...@icloud.com
>
>
>
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: no response to ticket #8901

[Mark Anderson]

April 23 - May 23 is one month.

—Mark
___
Mark E. Anderson 


On Sun, May 19, 2013 at 8:50 PM, David Strubbe  wrote:

> Yes, sorry I lost a digit, I do mean #38901. I agree it says "opened 4
> weeks ago" but it was created April 23. Since it is May 19, I count that as
> just 4 days short of two months. I am not sure how Trac reckons that as 4
> weeks.
>
> David
>
>
> On Sun, May 19, 2013 at 8:29 PM, Joshua Root  wrote:
>
>> On 2013-5-20 10:03 , David Strubbe wrote:
>> > Hello,
>> >
>> > There has been no response in 2 months from maintainer
>> > fabian.r...@googlemail.com  to
>> ticket
>> > #8901 which I filed about port libxc. Can the patch I submitted there
>> > please be reviewed and committed? These are minor issues, but it doesn't
>> > look like the maintainer is active anymore.
>> >
>> > Thanks,
>> > David
>>
>> No doubt you mean #38901. It's actually been open 4 weeks, not 2 months.
>> Maintainer timeout is 3 days in any case, so there's really no need to
>> exaggerate. :)
>>
>> - Josh
>>
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [MacPorts] #32907: tesseract @3.00_2+eng Not using leptonica

[Mark Anderson]

Can you attach the log it's talking about?  Probably config.log in
/opt/local/var/macports/
build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_tesseract/tesseract/work/tesseract-3.01

Thanks,
Mark

On Tue, Jan 17, 2012 at 12:16 PM, MacPorts  wrote:

> #32907: tesseract @3.00_2+eng Not using leptonica
>
> -+--
>  Reporter:  jack@…   |   Owner:  emer@…
> Type:  enhancement  |  Status:  new
>  Priority:  Normal   |   Milestone:
> Component:  ports| Version:  2.0.3
>  Keywords:   |Port:  tesseract
>
> -+--
>
> Comment(by jack@…):
>
>  Argh, it ate the formatting in my reply, sorry.
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #32075: Tesseract update to 3.01

[Mark Anderson]

I think your patch is the best we are going to do until 3.02 comes out,
which I am told is "soon".

Mark

On Mon, Jan 16, 2012 at 5:43 PM, MacPorts  wrote:

> #32075: Tesseract update to 3.01
>
> -+--
>  Reporter:  emer@…   |   Owner:  macports-tickets@…
> Type:  update   |  Status:  new
>  Priority:  Normal   |   Milestone:
> Component:  ports| Version:  2.0.3
>  Keywords:  maintainer haspatch  |Port:  tesseract
>
> -+--
>
> Comment(by ryandesign@…):
>
>  Where are we with this? Should I commit my patch, or do you have other
>  suggestions?
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #32075: Tesseract update to 3.01

[Mark Anderson]

Yeah, that might be the best. I was never that fond of the way we handled
it, but at the time this was the only choice. Subports sound like a great
idea.

Mark

On Tue, Nov 15, 2011 at 2:34 PM, MacPorts  wrote:

> #32075: Tesseract update to 3.01
>
> -+--
>  Reporter:  emer@…   |   Owner:  macports-tickets@…
> Type:  update   |  Status:  new
>  Priority:  Normal   |   Milestone:
> Component:  ports| Version:  2.0.3
>  Keywords:  maintainer haspatch  |Port:  tesseract
>
> -+--
> Changes (by ryandesign@…):
>
>  * cc: ryandesign@… (added)
>  * keywords:  => maintainer haspatch
>  * milestone:  MacPorts 2.0.4 =>
>
>
> Comment:
>
>  The revision should drop to 0 when the version is increased.
>
>  I think we can improve on this port w.r.t. the way the language files are
>  handled. It's not optimal the way it currently has to re-download the
>  language files when a new version of tesseract is released, even if they
>  haven't changed, and similarly, it has to re-download the tesseract source
>  if any of the language files change. Since this port was made, MacPorts 2
>  has been released, which has the new subport feature, and I think having a
>  separate subport for each language file would be the best solution. This
>  will also make it easier for users to decide later which language files
>  they need, without having to reinstall the main port.
>
>  Since subports are still new and not documented well, I'll see if I can
>  come up with a patch for your consideration.
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: Tesseract Upgrade

[Mark Anderson]

Sure. Sorry about that. Thought I was supposed to notify the list.

Mark

On Tue, Nov 15, 2011 at 2:15 PM, Ryan Schmidt wrote:

> On Nov 15, 2011, at 12:55, Mark Anderson wrote:
>
> > Can someone test and commit the Tesseract Upgrade.  It was pretty
> painless.
> >
> > https://trac.macports.org/ticket/32075
>
> You only filed the ticket 24 minutes ago... In future, please give us a
> few days to notice and deal with the ticket on our own before sending a
> message to the list.
>
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Tesseract Upgrade

[Mark Anderson]

Can someone test and commit the Tesseract Upgrade.  It was pretty painless.

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

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

tex-gantt checksum fail

[Mark Anderson]

Anyone else getting a checksum fail on tex-gantt in the repo, or is it just
me?

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

Re: Devtools opensource release

[Mark Anderson]

Also, do the raw system frameworks include the headers?  I don't have a
un-developer-tooled machine to look.

We could always resort to class-dump. :-)

Mark

On Fri, Mar 18, 2011 at 12:45 PM, William Siegrist wrote:

>
> On Mar 18, 2011, at 9:05 AM, Rainer Müller wrote:
>
> > On 03/18/2011 04:40 PM, Daniel J. Luke wrote:
> >> http://opensource.apple.com/release/developer-tools-40/
> >>
> >> so ... do we build/ship our own set of tools?
> >
> > As far as I can see this does not include any system headers which is a
> > showstopper.
>
>
> Maybe the Mac OS X releases[1] contain the headers you need? If you think
> the DevTools releases should have matching headers, let me know and I will
> look into it.
>
> [1] http://opensource.apple.com/release/mac-os-x-1066/
>
> -Bill
>
>
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: Xcode 4

[Mark Anderson]

So far I've been running XCode 4 with MacPorts and have not run into any
trouble.  I'll holler as soon as it causes a problem.

Mark

On Thu, Mar 10, 2011 at 8:23 PM, Dominik Reichardt wrote:

> >
> >>
> >>> I have to admit that I have no idea if and to which extent MacPorts
> >>> works with Xcode 4, as I didn't buy it (yet?
> >>
> >>
> >> I'm not sure how much MacPorts depends on the "lower" SDKs (10.4 and
> 10.5) or whether MacPorts depends on those at all, but Xcode 4 does away
> with those on every install. Meaning it moves old Xcode stuff, including
> those SDKs to /Developer-old and of course doesn't even give the option to
> keep these SDKs (or to install them on a System on which no Xcode was
> installed before).
> >> This is the most annoying issue with Xcode 4 for me, especially since I
> had moved the SDKs back, then installed Xcode 4 again (the one from the
> Appstore craps out in the last stages of the installation, but if you open
> the installer app you can start the installer on its own and it actually
> finishes) and I forgot to move the SDKs back and thus some compilation
> didn't succeed at first :)
> >
> >
> >
> > Even nicer as I just found out, the ld that comes with Xcode 4 is of
> course no longer threeway universal, missing the ppc part thus making it
> impossible to build ppc stuff (unless you use the one from the old xcode).
> > Highly annoying but when you find this out and circumvent it, you can
> actually compile PPC again... (you also need to put other
> /usr/libexec/gcc/powerpc-apple-darwin10/4.0.1 back as well)
> >
>
>
> Hmm, is there a way to set an alternate dynamic linker, something like
> "export ld=/usr/bin/ld_ppc_able", so to not mess with xcode 4 binaries? I
> couldn't find anything on google, except that this should work but it
> doesn't for a project of mine :(
>
> Dom
> ___
> macports-users mailing list
> macports-us...@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #26816: Update tesseract to version 3.00

[Mark Anderson]

A new diff has been attached that adds leptonica as a dependency. Give it a
shot, otherwise, I think this works.

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

Re: [MacPorts] #26816: Update tesseract to version 3.00

[Mark Anderson]

Can you attach a diff for the portfile?

Also, for the rest of the group, I'm probably going to need to add a
leptonica port, as this is probably the last tesseract that will compile
without it.  We'll probably want to add that soon too.

Mark

On Tue, Oct 12, 2010 at 9:13 AM, MacPorts  wrote:

> #26816: Update tesseract to version 3.00
>
> ---+
>  Reporter:  strom...@… |   Owner:  macports-tick...@…
> Type:  update |  Status:  new
>  Priority:  Normal |   Milestone:
> Component:  ports  | Version:  1.9.1
>  Keywords:  haspatch   |Port:  tesseract
>
> ---+
>  New version of tesseract released.
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

mdworker, etc

[Mark Anderson]

I've been noticing during long compiles on my older box, mdworker and
other spotlight goodies start eating CPU time.  Has anyone else
noticed this?  And if so, should we have an option to turn off
spotlight?  That might speed up some compiles on older boxes.

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

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  wrote:
> Is it possible to get the CPAN package Mac::Growl ported?
>
> Thanks
> ___
> macports-users mailing list
> macports-us...@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #24723: geda-gaf update to 1.6.1

[Mark Anderson]

Hey, thanks, I've been meaning to update this.

Mark

On Thu, Apr 29, 2010 at 5:34 PM, MacPorts  wrote:
> #24723: geda-gaf update to 1.6.1
> -+--
>  Reporter:  and.dam...@…             |       Owner:  e...@…
>     Type:  update                   |      Status:  new
>  Priority:  Normal                   |   Milestone:
> Component:  ports                    |     Version:  1.8.2
>  Keywords:  gpleda eda               |        Port:  geda-gaf
> -+--
>  Updated geda-gaf to 1.6.1 as per patchfile attached.
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #24445: tesseract universal build fails

[Mark Anderson]

ld -r -o libtesseract_full.o tesseractfull.o \
libtesseract_main.a \
../textord/libtesseract_textord.a \
../pageseg/libtesseract_pageseg.a \
../wordrec/libtesseract_wordrec.a \
../classify/libtesseract_classify.a \
../dict/libtesseract_dict.a \
../viewer/libtesseract_viewer.a \
../image/libtesseract_image.a \
../cutil/libtesseract_cutil.a \
../ccstruct/libtesseract_ccstruct.a \
../ccutil/libtesseract_ccutil.a
ld: warning: -arch not specified

This appears to be the problem...I'll take a look as to where that
link line gets constructed.  If anyone has ideas, let me know.

Mark

On Mon, Apr 12, 2010 at 3:16 AM, MacPorts  wrote:
> #24445: tesseract universal build fails
> -+--
>  Reporter:  ryandes...@…             |       Owner:  e...@…
>     Type:  defect                   |      Status:  new
>  Priority:  Normal                   |   Milestone:
> Component:  ports                    |     Version:  1.8.2
>  Keywords:                           |        Port:  tesseract
> -+--
>  Trying to build tesseract universal for x86_64/i386 on Snow Leopard fails:
>
>  {{{
>  --->  Building tesseract
>  DEBUG: Executing org.macports.build (tesseract)
>  DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.6'
>  DEBUG: Assembled command: 'cd
>  "/opt/local/var/macports/build/_Users_rschmidt_macports_dports_textproc_tesseract/work/tesseract-2.04"
>  && /usr/bin/nice -n 10 /usr/bin/make -j1 all'
>  /usr/bin/make  all-recursive
>  Making all in ccstruct
>  make[3]: Nothing to be done for `all-am'.
>  Making all in ccutil
>  make[3]: Nothing to be done for `all-am'.
>  Making all in classify
>  make[3]: Nothing to be done for `all-am'.
>  Making all in cutil
>  make[3]: Nothing to be done for `all-am'.
>  Making all in dict
>  make[3]: Nothing to be done for `all-am'.
>  Making all in pageseg
>  make[3]: Nothing to be done for `all-am'.
>  Making all in image
>  make[3]: Nothing to be done for `all-am'.
>  Making all in textord
>  make[3]: Nothing to be done for `all-am'.
>  Making all in viewer
>  make[3]: Nothing to be done for `all-am'.
>  Making all in wordrec
>  make[3]: Nothing to be done for `all-am'.
>  Making all in ccmain
>  /usr/bin/g++-4.2  -O2 -arch x86_64 -arch i386  -L/opt/local/lib -arch
>  x86_64 -arch i386 -L/opt/local/lib -o tesseract tesseractmain.o
>  libtesseract_full.a -ltiff -lpthread -ljpeg -lpng -lz  -lm
>  ld: warning: in libtesseract_full.a, file was built for unsupported file
>  format which is not the architecture being linked (i386)
>  Undefined symbols for architecture i386:
>   "TessBaseAPI::SetVariable(char const*, char const*)", referenced from:
>       _main in tesseractmain.o
>   "_page_image", referenced from:
>       _page_image$non_lazy_ptr in tesseractmain.o
>      (maybe you meant: _page_image$non_lazy_ptr)
>   "STRING::operator=(char const*)", referenced from:
>       _main in tesseractmain.o
>   "STRING::length() const", referenced from:
>       TesseractImage(char const*, IMAGE*, STRING*)in tesseractmain.o
>       _main in tesseractmain.o
>   "STRING::operator[](int) const", referenced from:
>       TesseractImage(char const*, IMAGE*, STRING*)in tesseractmain.o
>       TesseractImage(char const*, IMAGE*, STRING*)in tesseractmain.o
>       _main in tesseractmain.o
>   "BOOL_VARIABLE::BOOL_VARIABLE(unsigned char, char const*, char const*)",
>  referenced from:
>       __static_initialization_and_destruction_0(int, int)in
>  tesseractmain.o
>       __static_initialization_and_destruction_0(int, int)in
>  tesseractmain.o
>       __static_initialization_and_destruction_0(int, int)in
>  tesseractmain.o
>       __static_initialization_and_destruction_0(int, int)in
>  tesseractmain.o
>   "STRING::STRING()", referenced from:
>       _main in tesseractmain.o
>       _main in tesseractmain.o
>   "STRING::STRING(char const*)", referenced from:
>       TesseractImage(char const*, IMAGE*, STRING*)in tesseractmain.o
>       _main in tesseractmain.o
>   "BLOCK_zapper(ELIST_LINK*)", referenced from:
>       __Z12BLOCK_zapperP10ELIST_LINK$non_lazy_ptr in tesseractmain.o
>      (maybe you meant: __Z12BLOCK_zapperP10ELIST_LINK$non_lazy_ptr)
>   "STRING::string() const", referenced from:
>       TesseractImage(char const*, IMAGE*, STRING*)in tesseractmain.o
>       _main in tesseractmain.o
>       _main in tesseractmain.o
>       _main in tesseractmain.o
>       _main in tesseractmain.o
>   "STRING::operator+=(char const*)", referenced from:
>       TesseractImage(char const*, IMAGE*, STRING*)in tesseractmain.o
>       TesseractImage(char const*, IMAGE*, STRING*)in tesseractmain.o
>       _main in tesseractmain.o
>   "TessBaseAPI::SetInputName(char const*)", referenced from:
>       _main in tesseractmain.o
>   "ERRCODE::error(char const*, signed char, char const*, ...) const",
>  referenced from:
>       TesseractImage

Re: [MacPorts] #24446: tesseract segfaults with input filename extension tiff (was: tesseract segfaults)

[Mark Anderson]

I'll see if there are some upstream patches yet to fix this.

Mark

On Mon, Apr 12, 2010 at 3:36 AM, MacPorts  wrote:
> #24446: tesseract segfaults with input filename extension tiff
> -+--
>  Reporter:  ryandes...@…             |       Owner:  e...@…
>     Type:  defect                   |      Status:  new
>  Priority:  Normal                   |   Milestone:
> Component:  ports                    |     Version:  1.8.2
>  Keywords:                           |        Port:  tesseract
> -+--
>
> Comment(by ryandes...@…):
>
>  It doesn't segfault if I call the file "file.tif" instead of "file.tiff".
>  So this is the upstream [http://code.google.com/p/tesseract-
>  ocr/issues/detail?id=163 does not recognize .tiff extension] bug.
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Ticket #23774

[Mark Anderson]

I have added a PCB Portfile patch that brings it to the latest
version.  Can the maintainer/someone with authority test and commit
it?

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

Re: gEDA on MacPorts

[Mark Anderson]

That should probably be bumped to 20091103?  Submit a ticket on the
website ( http://www.macports.org ) asking for an upgrade.

I have a patch that might work, but Adam is the maintainer, so he'll
have to approve the changes.

Mark

On Tue, Dec 29, 2009 at 2:02 PM, Donald Tillman  wrote:
> [try again, 'goofed an email address]
>
> Gents,
>
> I understand you guys are maintaining the geda-gaf and pcb ports on
> MacPorts.
>
> I'm trying to set up and run gEDA (Mac PowerBook Pro, MAC OS X 1.5.8)
> and design some boards.  Fink has failed me, and so I'm trying to get
> the MacPorts version running.  (Specifically, Fink only has very old
> releases in binary form: gschem version 20071231, pcb version
> 20060822.  And Fink errors out with something incomprensible
> attempting to compile more modern versions.)
>
> I need a modern version of gschem because I need to use the path
> feature in the symbol files.  And I need a modern version of pcb
> because the version of gsch2pcb that I'm using generates files that
> are not compatible with pcb 20060822.
>
> So I'm looking to MacPorts.  MacPorts geda-gaf gives me a modern
> version of gschem, 20091004.  And that seems to work well.  But for
> some reason pcb isn't included in that package.  I discover that
> MacPorts pcb is a separate package, I try that, but it's pcb is only
> at version 20060321.
>
> So can you help?  How can I get a modern version of pcb?
>
> Thanks much.
>
>  -- Don
>
> --
> Don Tillman
> Palo Alto, California
> d...@till.com
> http://www.till.com
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Ticket #22512

[Mark Anderson]

Can someone please commit ticket 22512?  I have a diff attached that
should fix geda-gaf's problem.

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

Re: [MacPorts] #22512: geda-gaf 1.6.0 complains about missing update-desktop-database

[Mark Anderson]

I posted a diff with the workaround, gEDA doesn't really need it
anyway.  It did not error for me, however.  Did you build on Quartz or
X11, and do you have Gnome installed?

Mark

On Fri, Nov 13, 2009 at 8:20 AM, MacPorts  wrote:
> #22512: geda-gaf 1.6.0 complains about missing update-desktop-database
> +---
>  Reporter:  mich...@…               |       Owner:  e...@…
>     Type:  defect                  |      Status:  new
>  Priority:  Normal                  |   Milestone:
> Component:  ports                   |     Version:  1.8.1
>  Keywords:                          |        Port:  geda-gaf
> +---
> Changes (by j...@…):
>
>  * cc: e...@… (removed)
>  * owner:  macports-tick...@… => e...@…
>
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #22226: gEDA Port Submission

[Mark Anderson]

I see it attached.  Is it not building?

Mark

On Mon, Nov 9, 2009 at 11:30 PM, Frank Schima  wrote:
> Where is the new Portfile? It's not on the ticket.
>
>
> Cheers!
> Frank
>
> On Oct 28, 2009, at 8:13 PM, Mark Anderson wrote:
>
>> Ok, well I fixed it and added all 3 checksums to boot.  Can someone
>> commit it? Also, let me know if there are troubles.
>>
>> Mark
>>
>> On Tue, Oct 27, 2009 at 12:29 PM, Frank Schima
>>  wrote:
>>> Yes, post a new portfile, you should be able to overwrite the old one on the
>>> ticket.
>>>
>>>
>>> Cheers!
>>> Frank
>>>
>>> On Oct 27, 2009, at 7:46 AM, Mark Anderson wrote:
>>>
>>>> Ok, so I screwed this port file up a bit.  I forgot to add the
>>>> dependencies.   Should I post a new Portfile, or a diff.  Also, once
>>>> I've done that can someone commit it?
>>>>
>>>> On Sat, Oct 24, 2009 at 4:52 PM, MacPorts  wrote:
>>>>>
>>>>> #6: gEDA Port Submission
>>>>>
>>>>> ---+
>>>>>  Reporter:  e...@…         |       Owner:  macports-tick...@…
>>>>>    Type:  submission     |      Status:  new
>>>>>  Priority:  Normal         |   Milestone:  MacPorts 1.8.2
>>>>> Component:  ports          |     Version:  1.8.99
>>>>>  Keywords:  electronics    |        Port:
>>>>>
>>>>> ---+
>>>>>  Here is a Portfile to build the gEDA suite of tools.
>>>>>
>>>>> --
>>>>> Ticket URL: <http://trac.macports.org/ticket/6>
>>>>> MacPorts <http://www.macports.org/>
>>>>> Ports system for Mac OS
>>>>>
>>>> ___
>>>> macports-dev mailing list
>>>> macports-dev@lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>>>
>>>
>> ___
>> macports-dev mailing list
>> macports-dev@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #22226: gEDA Port Submission

[Mark Anderson]

Ok, well I fixed it and added all 3 checksums to boot.  Can someone
commit it? Also, let me know if there are troubles.

Mark

On Tue, Oct 27, 2009 at 12:29 PM, Frank Schima
 wrote:
> Yes, post a new portfile, you should be able to overwrite the old one on the
> ticket.
>
>
> Cheers!
> Frank
>
> On Oct 27, 2009, at 7:46 AM, Mark Anderson wrote:
>
>> Ok, so I screwed this port file up a bit.  I forgot to add the
>> dependencies.   Should I post a new Portfile, or a diff.  Also, once
>> I've done that can someone commit it?
>>
>> On Sat, Oct 24, 2009 at 4:52 PM, MacPorts  wrote:
>>>
>>> #6: gEDA Port Submission
>>>
>>> ---+
>>>  Reporter:  e...@…         |       Owner:  macports-tick...@…
>>>    Type:  submission     |      Status:  new
>>>  Priority:  Normal         |   Milestone:  MacPorts 1.8.2
>>> Component:  ports          |     Version:  1.8.99
>>>  Keywords:  electronics    |        Port:
>>>
>>> ---+
>>>  Here is a Portfile to build the gEDA suite of tools.
>>>
>>> --
>>> Ticket URL: <http://trac.macports.org/ticket/6>
>>> MacPorts <http://www.macports.org/>
>>> Ports system for Mac OS
>>>
>> ___
>> macports-dev mailing list
>> macports-dev@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #22226: gEDA Port Submission

[Mark Anderson]

Ok, so I screwed this port file up a bit.  I forgot to add the
dependencies.   Should I post a new Portfile, or a diff.  Also, once
I've done that can someone commit it?

On Sat, Oct 24, 2009 at 4:52 PM, MacPorts  wrote:
> #6: gEDA Port Submission
> ---+
>  Reporter:  e...@…         |       Owner:  macports-tick...@…
>     Type:  submission     |      Status:  new
>  Priority:  Normal         |   Milestone:  MacPorts 1.8.2
> Component:  ports          |     Version:  1.8.99
>  Keywords:  electronics    |        Port:
> ---+
>  Here is a Portfile to build the gEDA suite of tools.
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #19748: tesseract: fails doing "make install"

[Mark Anderson]

Yeah, I was going to do something similar. Thanks. I'll have to start
checking against Case-Sensitive file systems.

Mark

On Mon, May 25, 2009 at 1:15 AM, MacPorts  wrote:

> #19748: tesseract: fails doing "make install"
>
> +---
>  Reporter:  dam...@…   |   Owner:  e...@…
>   Type:  defect |  Status:  closed
>   Priority:  Normal |   Milestone:
>  Component:  ports  | Version:  1.7.1
> Resolution:  fixed  |Keywords:  make, install, java
>  Port:  tesseract  |
>
> +---
> Changes (by b...@…):
>
>  * status:  new => closed
>  * resolution:  => fixed
>
>
> Comment:
>
>  Replying to [comment:5 h...@…]:
>  > Leopard on Intel, Xcode 3.0 (though I think it's irrelevant). I still
>  think the case-sensitive filesystem is causing the makefile problem.
>
>  Note that there are issues with some of the tools shipped with Xcode 3.0
>  which are fixed in 3.1.x; though this isn't one of them.
>
>  It looks like there is a java/makefile on extract, which is overwritten by
>  Makefile during configure on case-insensitive filesystems; but obviously
>  not on case-sensitive, so the error occurs.  Fixed in r51430 (not awaiting
>  maintainer approval since it is broken for some).
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #19681: tesseract fails to stage

[Mark Anderson]

Can I get some more information on this? (OS, system, etc)

It builds fine on my machine. Not a whole lot goes on in the java directory.

Mark

On Fri, May 22, 2009 at 5:22 AM, MacPorts  wrote:

> #19681: tesseract fails to stage
>
> +---
>  Reporter:  h...@…  |   Owner:  e...@…
> Type:  defect  |  Status:  new
>  Priority:  Normal  |   Milestone:
> Component:  ports   | Version:
>  Keywords:  |Port:  tesseract
>
> +---
> Changes (by t...@…):
>
>  * version:  1.7.1 =>
>
>
> Old description:
>
> > Making install in java
> > make[1]: *** No rule to make target `install'.  Stop.
> > make: *** [install-recursive] Error 1
> >
> > Error: Status 1 encountered during processing.
>
> New description:
>
>  {{{
>  Making install in java
>  make[1]: *** No rule to make target `install'.  Stop.
>  make: *** [install-recursive] Error 1
>
>  Error: Status 1 encountered during processing.
>  }}}
>
> --
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #18077: tesseract: upgrade to 2.03

[Mark Anderson]

Whoops.  Uploaded a 2.03 diff.

Mark

On Mon, Jan 19, 2009 at 1:31 PM, MacPorts  wrote:
> #18077: tesseract: upgrade to 2.03
> ---+
>  Reporter:  ste...@…   |   Owner:  e...@…
> Type:  enhancement|  Status:  new
>  Priority:  Normal |   Milestone:  Port Updates
> Component:  ports  | Version:  1.7.0
>  Keywords: |Port:  tesseract
> ---+
>
> Comment(by macsforever2...@…):
>
>  This looks like version 2.01. It's best if you attach a
>  [http://guide.macports.org/#development.patches.portfile unified diff] of
>  the portfile, not a whole portfile. Thanks!
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #18077: tesseract: upgrade to 2.03

[Mark Anderson]

Ok, I've attached a new Portfile to the Ticket.  All that was needed
was a version and checksum update.  Try it out, and let me know if you
run into trouble.

Mark

On Sun, Jan 18, 2009 at 8:41 AM, MacPorts  wrote:
> #18077: tesseract: upgrade to 2.03
> ---+
>  Reporter:  ste...@…   |   Owner:  e...@…
> Type:  enhancement|  Status:  new
>  Priority:  Normal |   Milestone:  Port Updates
> Component:  ports  | Version:  1.7.0
>  Keywords: |Port:  tesseract
> ---+
> Changes (by j...@…):
>
>  * owner:  macports-tick...@… => e...@…
>  * type:  defect => enhancement
>  * milestone:  Port Bugs => Port Updates
>
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [MacPorts] #18077: tesseract: upgrade to 2.03

[Mark Anderson]

I'm on it.   I really don't think it should be a big deal.

Mark

On Sun, Jan 18, 2009 at 8:41 AM, MacPorts  wrote:
> #18077: tesseract: upgrade to 2.03
> ---+
>  Reporter:  ste...@…   |   Owner:  e...@…
> Type:  enhancement|  Status:  new
>  Priority:  Normal |   Milestone:  Port Updates
> Component:  ports  | Version:  1.7.0
>  Keywords: |Port:  tesseract
> ---+
> Changes (by j...@…):
>
>  * owner:  macports-tick...@… => e...@…
>  * type:  defect => enhancement
>  * milestone:  Port Bugs => Port Updates
>
>
> --
> Ticket URL: 
> MacPorts 
> Ports system for Mac OS
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev