Re: macOS Sierra / 10.12 support - where are we?
It looks like there's already a build bot running and several packages are already available to download. That's leagues ahead of past years. Is an installer coming soon? On Tue, Sep 20, 2016 at 4:01 PM, Sinan Karasu wrote: > If you install from sources, it works. > > Sent from my iPad > > On Sep 20, 2016, at 12:30, Kennedy, Smith (Wireless Architect) > wrote: > > Hello, > > Where is the MacPorts project concerning supporting macOS Sierra? The main > page doesn't mention it but I have to assume at least some users have been > testing MacPorts against the betas...? ETA for formal support? > > Thanks for any help, > > Smith > > > > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users > > > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users > -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: A screenshot/webpage capture app like Shutter?
On Thu, Feb 4, 2016 at 10:58 PM, bunk3m wrote: > @ryandesign, OSX does a great job at capturing an image of the screen but > what I'm looking for is the ability to capture the content, links and > pictures of a webpage. Most webpages are bigger than the screen (in length) > so the only way to capture using OSX screenshot is to capture a part, > scroll, capture another part and then join together using Gimp/Photoshop. You can also print and "Save as PDF" or "Export to PDF" directly from Safari. Or save the page as a "Web Archive". -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: New Mac OS Forge administrator
Congratulations. That's great news for everyone! On Thu, Nov 19, 2015 at 9:49 PM, Ryan Schmidt wrote: > Dear MacPorts users and developers, > > I'm pleased finally to be able to tell you that I have been hired to be your > new Mac OS Forge administrator. I have been involved in improving MacPorts > for years as a committer and as a manager, and now as a Mac OS Forge > administrator I will work on ensuring our infrastructure runs smoothly too. > > I apologize for the downtime we've experienced in the past months. My > priority right now is to resolve the existing issues, as I become familiar > with the systems. > > Please continue to report new problems with MacPorts infrastructure (server > not working) as you have before, using the server/hosting component in Trac > or via email to admin at macosforge dot org. And continue to report MacPorts > administrative issues (mailing list issues, commit access requests) to > portmgr at macports dot org. > > Thanks for your patience and support and thank you for using MacPorts. > > -Ryan > > > ___ > macports-dev mailing list > macports-...@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Experiences with El Capitan
I've been using this [1] procedure for quite a while. It could easily be adapted for widespread use by hosting the binaries and signatures somewhere publicly. And I'm not sure of the specifics, but I know there are build scripts in the repo somewhere for building all ports. A previous message [2] indicates they're here [3], But it looks like trac is still having issues. The real issue is trust. You have to trust the builder not to insert malware and the hoster to have secured the server against file manipulation. So I can see this easily being adapted for small groups, but I'd personally suffer through building everything myself over trusting an anonymous 3rd party. Apple has been very generous in their hosting and support previously, but I'd still love to see build slaves and hosting that wasn't reliant on them to manage. MacPorts can't possibly be a priority for their interests. [1]: https://trac.macports.org/wiki/howto/ShareArchives2 [2]: https://lists.macosforge.org/pipermail/macports-dev/2015-August/031253.html [3]: https://trac.macports.org/browser/contrib/buildbot On Mon, Nov 9, 2015 at 3:34 AM, Artur Szostak wrote: > Hi, > > Let me ask another question: Is there a seamless way to add building and > mirroring services from 3rd parties for the pre-built binaries? > > Kind regards. > > Artur > > > From: macports-users-boun...@lists.macosforge.org > [macports-users-boun...@lists.macosforge.org] on behalf of Daniel J. Luke > [dl...@geeklair.net] > Sent: 06 November 2015 16:08 > To: Rainer Müller > Cc: macports-users > Subject: Re: Experiences with El Capitan > > On Nov 5, 2015, at 3:35 PM, Rainer Müller wrote: >> This is mainly due to the absence of an actual admin at Mac OS Forge, >> our hosting provider at Apple. > > Do we know if there's a position posted? It would be great if someone from > the Macports community held that position. > > -- > Daniel J. Luke > ++ > | * dl...@geeklair.net * | > | *-- http://www.geeklair.net -* | > ++ > | Opinions expressed are mine and do not necessarily | > | reflect the opinions of my employer. | > ++ > > > > > > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Experiences with El Capitan
On Thu, Nov 5, 2015 at 3:00 PM, Dave Horsfall wrote: > Why did > it not merely retrieve pre-built binaries, as usual? Apple hasn't yet provisioned the build environment required for El Capitan binaries. There's a ticket somewhere tracking this issue, but I haven't seen any progress on it. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Two User-Experience Problems
On Thu, Aug 20, 2015 at 3:13 PM, Jean-François Caron wrote: > > 2) Since my OS is unusable during long builds, I walk away from the computer, > but then it goes to sleep the build is paused. The current advice is to get > a non-macports app called Caffeine to do some magic, or write a custom port > wrapper to use pmset noidle before and after the port command. This should > be an option in the MacPorts configuration somewhere, one shouldn’t have to > resort to 3rd-party apps or scripting to get user-friendiness out of MacPorts. "caffeinate" has been included since Mountain Lion (10.8) https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man8/caffeinate.8.html -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Where is AS located after Binutils is installed?
Check the output of: > port contents binutils On Thu, Apr 9, 2015 at 3:57 PM, Jeffrey Walton wrote: > I installed binutils in an effort to get the updated assembler. But I > can't seem to find it: > > $ sudo /opt/local/bin/port install binutils > ---> Computing dependencies for binutils > ---> Cleaning binutils > ---> Scanning binaries for linking errors > ---> No broken files found. > $ find /opt/local/ -name as > /opt/local//share/locale/as > > Where is AS located after binutils is installed? > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Am I supposed to use gem from MacPorts to install ruby packages in /opt/local/lib/ruby2.2/gems/2.2.0?
My ~/.gemrc includes: > install: --no-ri --no-rdoc --user-install > update: --no-ri --no-rdoc --user-install This directs gem to install inside my home folder rather than trying to install to a system or MacPorts location. Another bonus is that I don't have to use sudo. I still try install as much as I can using 'port' though. On Fri, Mar 20, 2015 at 10:31 PM, Peng Yu wrote: > Hi, > > If I use gem to install ruby packages, they will be installed in > /opt/local/lib/ruby2.2/gems/2.2.0 by default. But I guess ruby > packages installed by MacPorts will also use this directory. So this > may cause some problem, is it so? > > If so, what is the recommended way to install ruby packages via gem? Thanks. > > -- > Regards, > Peng > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [MacPorts] #47189: submission: audacity
On Wed, Mar 18, 2015 at 1:20 PM, René J.V. wrote: > On Wednesday March 18 2015 12:10:07 Arno Hautala wrote: > > So, no, there should be no fear of non-reproducible builds, at least not if I > got in all the dependencies :) > >> Regardless, I'd think the configure would still need to be set up to >> only use the internal or MacPorts versions. > > Which is what it does. Cool. I wonder if there's still an issue of sometimes using internal versions and sometimes using MacPorts, but as the internal versions aren't available yet, it seems like a minor issue if any. My internal pedant would want the configure to explicitly use the internal versions and explicitly select the available MacPorts versions, but the pedant must be crushed. Thanks for posting. I look forward to it being approved. --Arno -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [MacPorts] #47189: submission: audacity
On Wed, Mar 18, 2015 at 8:54 AM, René J.V. wrote: > There > are a few required components which are not in MacPorts and for which a > local version is used: libsms, libsoxr, libvamp, portsmf and widgetextra. > Audacity's configure script will detect and use the "system" versions when > available, so it will be easy to adapt the port if any of these are > considered useful beyond Audacity and added to MacPorts. Isn't this behavior to be avoided in ports? The configure script detecting these wont produce replicable builds. I'd think those features should be disabled until they are available in MacPorts. Or, by "local version" do you mean part of the Audacity source tree? Regardless, I'd think the configure would still need to be set up to only use the internal or MacPorts versions. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Why the executable binary of the aria2 download manager is named aria2c?
From: https://wiki.archlinux.org/index.php/aria2 > > The executable name for the aria2 package is aria2c. This legacy naming > convention has been retained for backwards compatibility. I don't know what legacy naming convention they're referring to, but… that's why? On Fri, Jan 30, 2015 at 8:59 PM, Behrang Saeedzadeh wrote: > Hi, > > Nothing important, but I have always wondered why the binary is named aria2c > rather than aria2? Was it clashing with another package that its executable > file was called aria2? > > Best regards, > Behrang > http://www.behrang.org > > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users > -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Is trac.macports.org down?
On Thu, Dec 18, 2014 at 10:15 AM, Daniel J. Luke wrote: > > why would homebrew pull the patch from trac.macports.org (instead of > svn.macports.org)? Whoever wrote that brewfile probably copied the build configuration from MacPorts, or copied just the patch when it became an issue. They just didn't bother to rehost it. On Thu, Dec 18, 2014 at 10:27 AM, Brandon Allbery wrote: > > Homebrew's been "reusing" stuff for a while now. It's a bit ironic, but aside from that, the potential for breakage when the patch changes, and the lapse in etiquette of not rehosting is there any problem here? Is the patch released under some license that would restrict reuse like this? I feel like Homebrew has backed down a bit from their initial hostility towards this project. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: questions regarding selfupdate issue
On Thu, Nov 13, 2014 at 8:45 AM, René J.V. wrote:
> On Thursday November 13 2014 14:04:06 Clemens Lang wrote:
>
>> one of the image tarballs. Some users do this in order to save space on an
>> SSD,
>> but doing so is wrong and dangerous.
>
> What, it's wrong and dangerous to make place by removing unused files? You
> ever use Swahili, Klingon and whathaveyou, or other less obscure languages
> you simply don't know but for which lots of ports add translations?
It's wrong and dangerous to meddle with files that are installed and
managed by a package system. The system expects files to be there and
doesn't know how to handle the case when they're missing. Granted,
port could be more helpful by indicating that the installation is
broken and maybe even offer to reinstall, ignoring any existing
archives.
> I agree one has to know what one does when going in and removing any file
> from a system; it would be nicer if the install procedure provided a way to
> prune this kind of useless space wasters.
Adding variant support to exclude excess languages would be a nice
feature. But, how much space are you really saving?
> In theory it should be fine to do this kind of pruning in ${destroot} before
> the installation phase, right?
That'd be better than trashing the files after they've been installed
and tracked by port. I wouldn't call it ideal or guaranteed not to
break.
>> You should uninstall and re-install all ports for which
>> images_to_archives.tcl
>> is triggered.
>
> Yeah, I figured that. Too many of them. I had a look at the script if I could
> "hack it in" to be done automatically, but it's too much unknown territory
> for me. My hunch I'd do it on a port-by-port basis when problems arise seems
> to be the way to go.
The easiest way would be to follow the migration instructions that
describe how to get a list of installed ports, uninstall everything,
and reinstall from your saved list.
--
arno s hautala/-| a...@alum.wpi.edu
pgp b2c9d448
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: "Updating database of binaries" step very slow under Yosemite?
On Wed, Oct 22, 2014 at 3:34 PM, René J.V. wrote: > > Also, I think it's a bit (much) overkill to scan all binaries when installing > a new or upgrading an existing port. In principle MacPorts knows which ports > depend on which other ports, and it knows what files a port contains. So it > shouldn't be overly difficult to scan only likely candidates for potential > dependency issues after an install or upgrade, and make the full, in-depth > scan something the user can execute when required (e.g. when instructed to do > so as part of a trouble-shooting procedure). I'm pretty sure that the scan only checks newly installed files. It certainly doesn't take multiple minutes every time on my system. I only saw a very long scan after re-installing all my ports after migrating to Yosemite. Subsequent scans have been much faster, respective of the size of the ports I've installed since. > I find that very often I simply interrupt the scanning process because I > don't want to have to wait for it. Aside from missing any broken ports until the next time you run the scan, I don't think this should have any detrimental impact on your installation. You could disable the scan with --no-rev-upgrade and run the command on its own (port rev-upgrade) once you're done installing ports; continuing your real work in another window. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: registry malformed after a kernel panic interrupted port build
Well, I may have fixed things for myself. With a few tips from this page: [1] I first tried dumping the registry and restoring to a new database. That got me a valid sqlite database, but it seemed to be missing some table definitions. So then I restored that old backup. That seemed to get things working, but completing my port upgrades yielded several files that were installed but not owned by a port. I'm assuming these were the ports that had been upgraded before the database went south. I forced the activation on those and was able to get everything installed. So far, things are looking good. Is there a reason that there isn't a journal for the registry.db? Or is there and I ran into some other issue? [1]: http://www.dosomethinghere.com/2013/02/20/fixing-the-sqlite-error-the-database-disk-image-is-malformed/ On Thu, Jun 26, 2014 at 11:51 PM, Arno Hautala wrote: > I just upgraded to 2.3.1 and experienced a kernel panic while later > upgrading ports. I'm fairly certain the panic was unrelated. > > Anyway, once booted I went to finish the port upgrades and found my > registry.db is now corrupt. > >> sqlite error: database disk image is malformed (11) while executing query: >> ATTACH DATABASE '/opt/local/var/macports/registry/registry.db' AS registry >> while executing >> "registry::open $db_path" >> (procedure "mportinit" line 610) >> invoked from within >> "mportinit ui_options global_options global_variations" >> Error: /opt/local/bin/port: Failed to initialize MacPorts, sqlite error: >> database disk image is malformed (11) while executing query: ATTACH DATABASE >> '/opt/local/var/macports/registry/registry.db' AS registry > > I did find tickets 32686 [1] and 36126 [2], but neither seems to have > a solution. One reply suggested that restoring from a backup may work > and I do have such a backup from a few days ago (probably the last > time I touched the port command). > > Will restoring from this backup leave things out of sync? I did > successfully upgrade a few ports before the panic, so I imagine some > port versions and installed files won't match. Is a reinstall of all > ports in my future? > > Thanks for any tips. > > --Arno > > [1]: https://trac.macports.org/ticket/32686 > [2]: https://trac.macports.org/ticket/36126 > > -- > arno s hautala/-| a...@alum.wpi.edu > > pgp b2c9d448 -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
registry malformed after a kernel panic interrupted port build
I just upgraded to 2.3.1 and experienced a kernel panic while later upgrading ports. I'm fairly certain the panic was unrelated. Anyway, once booted I went to finish the port upgrades and found my registry.db is now corrupt. > sqlite error: database disk image is malformed (11) while executing query: > ATTACH DATABASE '/opt/local/var/macports/registry/registry.db' AS registry > while executing > "registry::open $db_path" > (procedure "mportinit" line 610) > invoked from within > "mportinit ui_options global_options global_variations" > Error: /opt/local/bin/port: Failed to initialize MacPorts, sqlite error: > database disk image is malformed (11) while executing query: ATTACH DATABASE > '/opt/local/var/macports/registry/registry.db' AS registry I did find tickets 32686 [1] and 36126 [2], but neither seems to have a solution. One reply suggested that restoring from a backup may work and I do have such a backup from a few days ago (probably the last time I touched the port command). Will restoring from this backup leave things out of sync? I did successfully upgrade a few ports before the panic, so I imagine some port versions and installed files won't match. Is a reinstall of all ports in my future? Thanks for any tips. --Arno [1]: https://trac.macports.org/ticket/32686 [2]: https://trac.macports.org/ticket/36126 -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installing along Homebrew
On Thu, Jun 12, 2014 at 9:16 AM, Clemens Lang wrote: > Hi, > >> > Ideally it would check if the os already provides 1.9 and use that >> > one if it does, else depend on whatever ruby is already installed >> > by MP. >> >> Isn't that the type of non-reproduceable build that MacPorts tries to avoid? > > No. Either the OS has 1.9, then it's used (and never MacPorts' copy), or it > doesn't, then MacPorts' copy is always used. So the port does build > differently on different OS releases, but still doesn't depend on anything > installed or configured by the user. We would certainly want to avoid using > MacPorts ruby if it's there and system ruby if it isn't. Gotcha, I missed that the check would be based on the OS and not just the presence of Ruby. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installing along Homebrew
On Thu, Jun 12, 2014 at 3:08 AM, Mojca Miklavec wrote: > > Ideally it would check if the os already provides 1.9 and use that > one if it does, else depend on whatever ruby is already installed > by MP. Isn't that the type of non-reproduceable build that MacPorts tries to avoid? -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: installed tree on Mavericks 10.9.2
On Wed, Apr 23, 2014 at 1:27 PM, Ken G. Brown wrote: > > Now that tree apparently is installed, how do I run it, where is the > executable? The executable is probably installed at /opt/local/bin/tree You can check for sure using "port contents tree" > Is there something I am missing in setting up to be able to run the MacPorts > installed programs? I'm guessing that you didn't realize that "tree" is a command line utility, as is most of the software provided by MacPorts, though there are some graphical wares. "tree" and the "port" command that I listed above can be run from Terminal.app. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: port command & arguments
On Fri, Apr 11, 2014 at 3:21 AM, René J.V. wrote: > An alias subsitution that replaces a certain argument of a given command > regardless of what order arguments have been passed, and their order? I think this is indeed a feature of ZSH. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: usage numbers for macports vs. homebrew?
On Tue, Mar 18, 2014 at 9:56 PM, Eric A. Borisch wrote: > I wrote a little script for myself that goes and queries > packages.macports.org and determines if a port will be built or use a > package; it spits out a dot graph of dependencies colored by which is going > to happen. > I'd love to see that. Is the script available? -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: usage numbers for macports vs. homebrew?
On Tue, Mar 18, 2014 at 9:39 PM, Craig Treleaven wrote: > Our 'extra steps', seem to trip up at least half our new users. Another big one would be handling major OS upgrades more cleanly. I think the two issues are that MacPorts detects certain configurations upon install and generally all ports need to be rebuilt. Making MacPorts detect the OS upgrade, re-detecting and reconfiguring as necessary, and then handling the rebuild would solve a lot. Plus, it'd be nice if the buildbot was setup on the new OS prior to release. It's a pain that MacPorts doesn't support the latest OS until a few days / weeks after it's out. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: usage numbers for macports vs. homebrew?
On Tue, Mar 18, 2014 at 7:48 PM, Clemens Lang wrote: > For less than 10 results, the following looks nice to my eyes: > >>gt; port search git > portversion description > --- --- > babl-devel 0.1.11-20140305 Babl is a library for dynamically handling pixel > formats and managing conversions between them. > This is the development version based on a recent > snapshot of upstream git master. > bitcoin 0.8.6client user interface for a peer-to-peer > digital currency (yes, we also print > useless matches like these) > etc. How about: > babl-devel 0.1.11-20140305 Babl is a library for dynamically handling pixel formats and ... > bitcoin 0.8.6client user interface for a peer-to-peer digital currency ... -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: usage numbers for macports vs. homebrew?
On Tue, Mar 18, 2014 at 5:43 PM, Ryan Schmidt wrote: > Also, consider the OS X startup progress bar, back when OS X had one: > originally it was very accurate, but by Tiger it had been changed to just > advance at a more or less constant rate regardless what was happening; the > boot process frequently would complete before the progress bar had gotten to > the end. Just some indication that something is happening is useful to the > user, even if it’s not completely accurate. I thought I remembered hearing that it worked by timing the previous boot and using that to calculate the current boot progress. That's fairly similar to the line counting idea. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: usage numbers for macports vs. homebrew?
On Tue, Mar 18, 2014 at 6:42 AM, Clemens Lang wrote: > - homebrew doesn't try as hard as MacPorts to make builds reproducible. If > you install vim, it'll use the first python available. When that's system > python it uses that, if it's homebrew python it'll use that (and if its > MacPorts python, well you get the idea) I'm pretty sure they consider this a strength. "I already have Python! Why is MacPorts trying to install a new version!?" > - homebrew doesn't have privilege separation and sandboxing like MacPorts > does (they make a case that sudo is bad, so they can't use any of those, > making their setup arguable less secure than ours). I'm always conflicted on this one. On the one hand, most users are probably the primary user on their machine, so installing to /usr/local without privledges is probably not the worst thing in the world. On the other, security is a chain of links and this is definitely one that has been weakened. It would not be the worst thing in the world to eliminate the need for root in MacPorts. I know there have been changes in the past related to this, and I'm not sure what the current state of things is. I think for the most part, you can install an un-privledged MacPorts to a non-default location. Overall, I feel like HomeBrew came around when MacPorts was established to the point where enough people were using it that there were plenty of complaints about one feature or another and HomeBrew was able to capitalize on that. GitHub was the new exciting place to be as well. It's unfortunate that a direct attack on MacPorts was the best way to attract a userbase, but I have to feel it helped them more than hurt. (The slogan and a port that installed from SVN head in order to stay up to date were the things that turned me off when I gave it a chance.) -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: list active ports with non-default variants
On Thu, Mar 6, 2014 at 12:48 PM, Bradley Giesbrecht wrote: > Does anyone have a command for listing active ports with non-default variants? I'm not aware of any, but I'd love to find there is one. I usually end up dumping a list of installed ports to a file and then removing variants that I know are in my default configuration. Then I go port by port, comparing what's left. I'd love a command like "port installed --without-default-variants" that would omit variants that are enabled by befault by the port or user configuration. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript
On Wed, Feb 12, 2014 at 10:04 AM, Gregory Shenaut wrote: > I understand why installing in /usr/local can mess up macports, but macports > doesn't have everything, and most third-party software wants to go into > /usr/local. Where should this stuff go, if not /usr/local? I install everything into my home folder. > ./configure --prefix=~/local/ > make && make install If you need it available system-wide, just pick some other custom location (ie. /custom/). In any case, just make sure you're consistent (update your PATH) and point your configure script to the right place if the software can't find the libraries in your path or you need to override libraries that are in your path. The longer answer is that I use stow (http://www.gnu.org/software/stow/ ; and available in MacPorts) to assemble the bin, man, etc. directories. Stow isn't required, but it does help manage the software that isn't being managed by MacPorts. So, I might install a piece of software with: > ./configure --prefix=~/local/stow/foo-1.2.4 > make && make install > cd ~/local/stow > stow foo-1.2.4 Stow just allows you to easily add and remove versions of software by linking a hiearchy of directories into a common location. I might have foo-1.2.4, foo-1.2.6, bar-3.9, but only have foo-1.2.4 and bar-3.9 active. I can the upgrade to foo-1.2.6 by running: > cd ~/local/stow > stow -D foo-1.2.4 > stow foo-1.2.6 > rm -rf foo-1.2.4 -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem with Macports, homebrew, and ghostscript
On Tue, Feb 11, 2014 at 4:12 PM, Art McGee wrote: > Homebrew is mainly intended to be used by developers who use their system > almost exclusively for development. They are unconcerned with the effects of > mucking with /usr/local and it's ownership or permissions. I know this is getting off topic, but I disagree with this assessment. While I'm sure there are developers that use Homebrew, I think the primary audience is the average user who "just wants it to work" (I'm sure that demographic includes developers as well). Specifically, the user who doesn't understand why MacPorts is taking so long to install so many things when all they want is one tool. They're probably already running as an administrator and are the only user on the system, so who cares if /usr/local is set world writeable? From a certain point of view, that seems valid, but it does ignore the reasons that led to MacPorts' "complexity" and the steps that MacPorts has taken to mitigate some of those concerns (ie. pre-built packages). -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to associate /opt/local/bin/bash with .bat files
On Tue, Jan 28, 2014 at 8:40 AM, Clemens Lang wrote: > Macs (and other Unix systems) don't associate files and their > interpreters based on the filename extension. Only windows uses this > method. That's not entirely true. Macs used to use File Type and Creator codes to associate files and in those days extensions weren't required on file names. These attributes are still visible via commands like GetFileInfo. Their use is certainly deprecated and I wouldn't be surprised if it isn't consulted at all in current versions of OS X. Seems that as of 10.6 they're ignored in favor of Uniform Type Identifiers: http://en.wikipedia.org/wiki/Creator_code I'm fairly sure that the current mix of UTI and extension mapping is a mess though. At least, it seemed to be the last time I looked into it. That's another thread though. These days, if you Get Info on a file (select the file in the Finder and use Command-I or File > Get Info) there is a section labeled "Open With". You can select an application from the list or explicitly browse to some other application. When changing the selection, there's a button to "Change All". Pressing that will prompt to associate "all files with extension '.bat'" with the new application. Some extensions are associated with known types, and some files are marked with UTIs, and will instead ask if you want to associate, for example, all "text files" instead of listing ".txt". In your case though, you wouldn't want to associate a ".bat" or ".sh" file with bash, you'd want to set it to be opened by "Terminal.app". You can then edit the shebang line to set which shell should be used to interpret the script, as indicated by Clemens. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Find which port a file is from?
port provides On Sat, Jan 11, 2014 at 12:16 AM, Peng Yu wrote: > Hi, > > I don't find a command that can show which port a file is from. This > function is available in apt-get on ubuntu, I guess similar things > should be available on macports. Could anybody let me know if there is > a way to do it? Thanks. > > -- > Regards, > Peng > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Minimising MacPorts Internal Disk Usage
On Thu, Aug 15, 2013 at 9:16 AM, Ryan Schmidt wrote: > > If you want to combine those two operations into a single command, it's: > > sudo port -u upgrade outdated Ah, good point. I don't recall why I had them split out like that. Restricting commands to single actions? Ignorance? I don't know. Thanks. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Minimising MacPorts Internal Disk Usage
On Thu, Aug 15, 2013 at 8:59 AM, "René J.V. Bertin" wrote: > > On Aug 15, 2013, at 10:33, Chris Jones wrote: >> >> port uninstall inactive > > I tried that once, and had to restore my whole installation tree from backup. > I would be great if one could uninstall all old versions except for the > previous version! It's not exactly what you're looking for, but you could run: port uninstall inactive and actinact "actinact" is only those ports that have an active version as well as an inactive version. Combining it with "inactive" means install any inactive ports that also have an active version. I use it after running "upgrade outdated" to remove the old versions of ports, while leaving in place anything that I've manually left inactive. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Visualized MacPorts Ports
You might also look at this:
http://www.puredarwin.org/developers/macports/macports-dependencies-overview
On Wed, Jul 3, 2013 at 12:45 PM, Rainer Müller wrote:
> On 2013-07-03 18:16, Jean-François Caron wrote:
>> I'm wondering if there is a MacPorts equivalent to the python-apt
>> package, for getting MacPorts information directly within python. Or
>> otherwise a good way to access the MacPorts list of ports,
>> dependencies, and categories from Python.
>
> There is no API for Python. However, you can query the information
> straight-forward with the port tool.
>
> List of all available ports:
> port -q echo all
>
> List of all dependencies of a specific port:
> port -q echo depof:$NAME
>
> There is no such thing as suggest/recommends in MacPorts, but it still
> has different kinds of dependencies. On the one hand there are
> depends_fetch, depends_extract and depends_build, that are only required
> for building the port. On the other hand there are depends_lib and
> depends_run which are required at runtime. The command above using
> depof: includes all of them.
>
> I guess it's more interesting to see runtime dependencies for such a
> graph, but you could also add both build and runtime dependencies with a
> different weight as in the graph for Ubuntu. Anyway, we should
> distinguish between these two types of dependencies.
>
> Retrieving only the runtime dependencies of a specific port in a nice
> line-wise format proves to be a lot harder:
>
> port -q info --depends_lib --depends_run $NAME |tr ',' '\n' |awk -F: 'NF
>> 0 {print $NF}'
>
> I hope that helps you to get started for a similar project. In case you
> need more assistance with the port command, just ask :-)
>
> Rainer
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
--
arno s hautala/-| a...@alum.wpi.edu
pgp b2c9d448
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Correct crontab entry for port selfupdate && port upgrade outdated
The basics are that the shell script goes in /usr/local/bin (or anywhere else really, just make sure you edit the plist to point to where the script is). The plist goes in `/Library/LaunchDaemons/`, should be owned by root:admin and have 644 permissions. You can then load the service with: `launchctl load /Library/LaunchDaemons/org.macports.port.selfupdate.plist` and stop the service with "unload" instead of "load". For detailed info, read this: http://web.archive.org/web/20120415040038/http://www.afp548.com/article.php?story=20050620071558293 On Sat, Apr 27, 2013 at 10:21 PM, Peng Yu wrote: > Hi, > > Where should I put these files and what commands shall be used to load them? > > On Sat, Apr 27, 2013 at 8:55 PM, Arno Hautala wrote: >> I use the following launchd task [1] and shell script [2] to automate >> weekly updates. >> >> You can remove the reference to "portsign.sh", unless you want to >> share your compiled ports with another MacPorts installation [3]. >> >> [1]: https://gist.github.com/fracai/2324512 >> [2]: https://gist.github.com/fracai/2324493 >> [3]: https://trac.macports.org/wiki/howto/ShareArchives2 >> >> >> On Sat, Apr 27, 2013 at 5:55 PM, Clemens Lang wrote: >>> On Sat, Apr 27, 2013 at 04:16:50PM -0500, Ryan Schmidt wrote: >>>> And running MacPorts via root instead of via sudo will currently cause >>>> some problems: >>>> >>>> http://trac.macports.org/ticket/34221 >>> >>> You could use the workaround I proposed in >>> https://lists.macosforge.org/pipermail/macports-dev/2013-April/022725.html >>> (the mail is a reply to a mail that seems to have been moderated from >>> the list, which is the reasons why it seems to be lacking some context) >>> >>> -- >>> Clemens Lang >>> >>> ___ >>> macports-users mailing list >>> macports-users@lists.macosforge.org >>> https://lists.macosforge.org/mailman/listinfo/macports-users >> >> >> >> -- >> arno s hautala/-| a...@alum.wpi.edu >> >> pgp b2c9d448 >> ___ >> macports-users mailing list >> macports-users@lists.macosforge.org >> https://lists.macosforge.org/mailman/listinfo/macports-users > > > > -- > Regards, > Peng -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Correct crontab entry for port selfupdate && port upgrade outdated
I use the following launchd task [1] and shell script [2] to automate weekly updates. You can remove the reference to "portsign.sh", unless you want to share your compiled ports with another MacPorts installation [3]. [1]: https://gist.github.com/fracai/2324512 [2]: https://gist.github.com/fracai/2324493 [3]: https://trac.macports.org/wiki/howto/ShareArchives2 On Sat, Apr 27, 2013 at 5:55 PM, Clemens Lang wrote: > On Sat, Apr 27, 2013 at 04:16:50PM -0500, Ryan Schmidt wrote: >> And running MacPorts via root instead of via sudo will currently cause some >> problems: >> >> http://trac.macports.org/ticket/34221 > > You could use the workaround I proposed in > https://lists.macosforge.org/pipermail/macports-dev/2013-April/022725.html > (the mail is a reply to a mail that seems to have been moderated from > the list, which is the reasons why it seems to be lacking some context) > > -- > Clemens Lang > > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Python pip issue
On Wed, Apr 3, 2013 at 1:18 AM, Ned Deily wrote: > > Also make sure you don't have a permissions problem. If you did a "sudo > pip install", the created directories and files may not be world > readable and executable. Check and, if necessary, alter the > permissions of the packages you installed: Also, I think it's generally a bad idea to let pip install stuff into the MacPorts prefix. Now you've got two package managers dumping stuff into the same directories. It's entirely possible that one of them could delete or overwrite files that were being managed by the other system and now you've got broken dependencies. Instead, you can tell pip to install into your user prefix. This was the first hit on Google: http://stackoverflow.com/questions/7143077/use-pip-and-install-packages-at-my-home-folder# Note the discussion regarding where the libraries will be installed under different versions of python, which leads to how I'm managing things with ~/.pip/pip.conf. I have: > [install] > build-directory = /tmp/pip/ > install-option = --prefix=~/local/ Then make sure that local prefix is in your path and you should be good. There's also no need to use sudo with these options. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: A growl about Growl (and NSAlert?)
I just wanted to note that while the Growl software is now sold on the AppStore, the source is still available. http://growl.info/documentation/developer/growl-source-install.php http://code.google.com/p/growl On Fri, Feb 8, 2013 at 2:27 AM, Ryan Schmidt wrote: > > On Feb 7, 2013, at 23:26, Ian Wadham wrote: > >> I have been trying to get Pallet (MacPorts GUI) working in my environment: >> OS X 10.7.5 (Lion) and Xcode 4.6, but it is badly broken. One large problem >> is that there is no feedback re whether a request has succeeded or failed or >> what went wrong if it failed. >> >> I think this is because Growl @1.1.6 is not installed (although it is not >> listed >> as a dependency of Pallet). The Pallet code is certainly referencing its >> Growl >> interface and providing text strings, whenever a MacPorts action finishes. >> But nothing happens. >> >> I tried to install Growl @1.1.6, but the installation failed. See attached >> log. >> >> Browsing around the Growl website, it appears Growl has moved on quite >> a lot since v1.1.6 and is now v2.0.1, for Lion and Mountain Lion, for $4.99 >> in the App Store. It has been chargeable since Growl 1.3. See: >> >>http://growl.info/downloads --- and the apalogia on: >>http://growl.posterous.com/growl-13-a-summary-of-the-major-changes >> >> It is claimed to be Open Source, but it is not free (as in beer). >> >> I tried to find out if any other MacPorts ports use Growl, but could not. >> The "port dependents" command only applies only to installed ports. >> >> The question is whether I should persist with Growl? Maybe whether MacPorts >> should persist with Growl or just discontinue its very old version? >> >> Should I switch to Cocoa's NSAlert, which apparently is OS X's version >> of a popup message box? Growl has some additional nice features, like >> being able to look back over history. NSAlert seems rather basic, but I >> can certainly use it to continue testing and finding out how much Pallet >> actually does for the end-user. > > Users should not be required to use Growl; Growl should be optional. Users > who want Growl features can install Growl; those who don't won't be bothered. > > I have Growl 1.2.2 installed on Mountain Lion (manually, outside of > MacPorts); works great for me (for purposes unrelated to Pallet). I like it > when software supports Growl. > > Note that Pallet includes its own copy of the Growl framework. We have a > ticket about that being a bad idea, and wanting it to use a central copy of > the Growl framework: https://trac.macports.org/ticket/27180#comment:13 > > Growl having switched from free open source to paid has put a kink in > MacPorts' plans. Not sure how we should handle the Growl port going forward. > We would at least like to update it to the latest free version: > https://trac.macports.org/ticket/22684 > > The error you showed in your log building growl 1.1.6 is well-known; see > https://trac.macports.org/ticket/32911 > > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: encryption tool for Microsoft SkyDrive
You could use GPG and 'split'. You could also just create a sparse bundle Disk Image (the default band size is 8 MB) and put your files in that. Both options are going to rely on what is acceptable for your needs. On Sat, Jan 12, 2013 at 2:21 PM, Markus Neuenschwander wrote: > I use Microsoft SkyDrive web gui and upload a bunch of 10 - 60 MB movies. > There is an upload file size limit for individual files. I wish to encrypt > files and file names with password (not strong cryptographic). > > any good tool in MacPorts? > ___ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: FreeBSD partition
On Tue, Nov 13, 2012 at 5:20 AM, Raoul wrote: > > is there a way to mount "WR" or at least "R" a FreeBSD partition > on osx 10.8XX??? I assume you're talking about a UFS partition. I wanted to do the same recently and while OS X should support UFS, I've found that there are two flavors of UFS that differ in endianness. FreeBSD uses little endian and OS X uses big, even on Intel. I have not found a way to share data between OS X and FreeBSD using UFS. Now that Zevo [1] is available though, you could use ZFS, though I imagine the issue is that the data is already on a UFS partition and you're hoping to recover that data. [1]: http://www.getgreenbytes.com/zevo/ -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Is Goldendict available for Macports?
On Fri, Aug 31, 2012 at 9:29 AM, Mojca Miklavec wrote: > On Fri, Aug 31, 2012 at 3:15 PM, Arno Hautala wrote: >> >> I don't see any sort of documentation relating to how to compile anything. > > http://goldendict.org/buildfromgit.php > >> In fact, their .gitignore file [2] specifically excludes the Makefile >> from being checked into the repository. > > That's probably because one should use qmake first which generates > system-dependent makefiles, in the same way as ./configure does. Heh, whoops. Thanks. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Is Goldendict available for Macports?
On Fri, Aug 31, 2012 at 6:53 AM, Gustavo Benedito Reis Costa wrote: > > I would like to compile and run GoldenDict via Macports via terminal. > I use Mac OS X 10.8.1 Mountain Lion. > > Is it available for Macports? If not, how to compile and install it? This may be best taken up with the GoldenDict developers. I took a quick look at their site and githup repository [1] and I don't see any sort of documentation relating to how to compile anything. In fact, their .gitignore file [2] specifically excludes the Makefile from being checked into the repository. I'm not familiar with the project, so maybe that's normal there, but it seems like they're making things difficult for others to compile their work. [1]: https://github.com/goldendict/goldendict/ [2]: https://github.com/goldendict/goldendict/blob/master/.gitignore -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Monitoring Internet Usage
On Wed, Aug 1, 2012 at 1:44 PM, Arno Hautala wrote: > > [...] Rubbernet [3] are options that show these stats, but I'm not sure if > you can monitor their stats from across the network. > > [...] > > [3]: http://rubbernetapp.com/ Just wanted to clarify that looking at their site indicates that remote monitoring is supported. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Monitoring Internet Usage
On Wed, Aug 1, 2012 at 1:14 PM, Bradley Giesbrecht wrote: > > Have you looked at vnstat? That would show bandwidth usage, but not on a per app basis. Ideally, this would be something like nethogs [1], but that's not compatible with OS X. LittleSnitch [2] and Rubbernet [3] are options that show these stats, but I'm not sure if you can monitor their stats from across the network. If you're running one of the Lions on your machine and his, you could log in as a concurrent user to your sons machine to monitor these stats. There's also directly asking him. Let him know that the usage is an issue, you're looking into it, and he'll be responsible for any overages that he causes. [1]: http://nethogs.sourceforge.net/ [2]: http://www.obdev.at/products/littlesnitch/index.html [3]: http://rubbernetapp.com/ -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: -p considered problematic (was Re: how to proceed past errors?)
On Tue, Jul 31, 2012 at 12:17 PM, Jeremy Huddleston Sequoia wrote: > > IIRC, the OP was talking about upgrade, not install. So in your case, you > would have: > > port -p upgrade upgrade port-a > > This is problematic because port-a will be upgraded even through port-d > failed. If port-a was rev-bumped specifically because of port-d to force a > rebuild after the port-d install, this will thwart that. Luckily, > rev-upgrade now exists to work around such issues these days, but I still do > not recommended '-p upgrade' Ah, good point. So if '-p upgrade' causes such a problem, upgraded port-a, outdated and incompatible port-d, does rev-upgrade leave the now broken port-a in place if port-d and port-a can't be properly built? Or does it leave the broken port? I've watched rev-upgrade before, but I can't remember if it uninstalls the broken ports before rebuilding or if it only uninstalls them when the rebuild succeeds. Thanks, --Arno -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: -p considered problematic (was Re: how to proceed past errors?)
On Tue, Jul 31, 2012 at 11:05 AM, Jeremy Lavergne wrote: > > I don't think that's a problem with -p, however it will be more likely to > manifest itself that way; it's more of a bug with the port that's allowing > that opportunist linking or otherwise incorrectly declared dependencies. Gotcha, thanks. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
-p considered problematic (was Re: how to proceed past errors?)
On Thu, Jul 26, 2012 at 12:43 PM, Jeremy Huddleston Sequoia wrote: > > On Jul 26, 2012, at 09:41, "Daniel J. Luke" wrote: > >> From the man page: >> >> -p Despite any errors encountered, proceed to process multiple >> ports and commands. > > That is *very* problematic. Don't do it unless you really, really, really > know what it implies. Why is this considered problematic? My understanding is that this won't allow a port to be installed if it's dependencies fail, but will continue to build as many requested ports as is possible. ie: port-a depends on port-b, port-c, and port-d > port install port-a would install port -b, port-c fails, and port stops > port -p install port-a would install port-b, port-c fails, install port-d, doesn't install port-a because deps aren't satisfied. I've been using this flag in an automated process for quite some time. What problems should I be aware of with using this switch? -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: noidle
On Thu, Mar 22, 2012 at 4:00 AM, Drechsel Wolf wrote: > > frequently I noticed that my iMac G5 will go to sleep during a time > extensive build (gcc45 at the moment). >> pmset noidle & This won't be of help to the G5, but Mountain Lion introduced a new command called 'caffeinate' [1]. i.e.: > caffeinate -s port install gcc45 [1]: http://www.manpagez.com/man/8/caffeinate/ -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: What has MacPorts Installed for py27-iPython?
On Sat, Jul 7, 2012 at 2:37 PM, Jamie Paul Griffin wrote: > On Sat, Jul 07, 2012 at 10:19:28AM -0400, Arno Hautala wrote: > >> It might be better to link into ~/local/bin or somewhere else that's >> completely under your control. > > It wasn't a port though, I built pyzor from source only I used the port > built python2.7 to build it so I can't forsee any issues there but it's a > good point > to remember none the less. Maybe i'm wrong, though? Ah, gotcha. But, yeah, even in that case installing anything into the MacPorts prefix that wasn't put there by MacPorts could cause problems if MacPorts notices it. Unless you're prepared to handle whatever issues crop up. It's just a pain when someone does something not supported and then wants support. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: What has MacPorts Installed for py27-iPython?
On Sat, Jul 7, 2012 at 9:57 AM, Jamie Paul Griffin wrote: > > I experienced a similar issue when I installed pyzor (not from Macports > but build manually using the Macports installed python2.7) and the > binary pyzord was installed in: > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/pyzord > > You can just use a symlink to the binary into a directory in your path; > /opt/local/bin for example. It's probably not a good idea to put anything in /opt/local/bin If you link it as bin/pyzord, for example, and that port later starts linking into bin on it's own, you'll receive an activation error, and you'll most likely have forgotten that you linked it yourself and not understand the error. (apologies for any assumptions about your technical memory skills) It might be better to link into ~/local/bin or somewhere else that's completely under your control. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: binaries list
On Tue, Jul 3, 2012 at 7:38 PM, Gregory Seidman wrote: > On Tue, Jul 03, 2012 at 07:09:17PM -0400, Jeremy Lavergne wrote: >> That's how it just works. > > Well, no, it doesn't just work. I want to issue a single port command, e.g. > port upgrade outdated, and have it install binaries where available and > install anything else from source. I want to *prefer* binaries without > *restricting* to binaries. As others have stated, this should be the default behavior. The example commands that I posted would only really be useful if you wanted to delay compiling a large install for some reason. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: binaries list
On Tue, Jul 3, 2012 at 10:52 AM, Jeremy Lavergne wrote: >> yes, but that would only work if a binary is available! > > Yes, but it'll do what you're after: letting you know if one is available. > > You can add -p if you want it go on and do what it can from a list of ports > you want to install without bailing at first error. Good idea, so say you want to install some set of ports, one of which has many deps: > port -p -b install port1 port2 port3 big-port port1 port2 go in fine, port3 isn't available as a binary and one of the deps of big-port isn't available. You can then check what's missing with: > port echo port1 port2 port3 big-port rdepof:big-port and not installed You would see something like: > port3 > big-port > big-port-dep1 You can then install the ports that you have to manually compile when you have the processor time: > port install port3 big-port -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: binaries list
On Tue, Jul 3, 2012 at 10:01 AM, Federico Calboli wrote: > > is there a list of which ports are available as a binary (for Lion)? You can browse this page: http://packages.macports.org/ I think there is a script that can be used to query a Portfile's license as well, but just because a port's license allows distribution doesn't mean a binary is available or is the current version that would be installed by 'port'. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How to best clean old Perl installations directories
On Mon, Jul 2, 2012 at 9:54 AM, Rodolfo Aramayo wrote: > > /opt/local/lib/perl5/ > I have the following directories: > > [...] > > Why where the Perl 5.12 directories not removed? > Is there a safe way or proper way to removed these directories? Are those directories empty? Do you still need any of the p5.12 ports? They wouldn't have been automatically removed by just installing the 5.14 versions. You should be able to see what ports are installed with: port installed p5.12-* You could then remove all of those, except for any that are deps of other installed ports with: port -p uninstall p5.12 The '-p' should keep the uninstall going even if there are some that can't be removed. In general, you should only interact with MacPorts installed files through the port command. It's typically best to not manually cleanup the opt directory. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Have I misunderstood what leaves are?
On Thu, Jun 28, 2012 at 11:18 AM, Brandon Allbery wrote: > > A leaf is an *unrequested* port without dependents, i.e. the unwanted > dependencies left behind when you remove a port that you explicitly > installed (and hence had the requested flag set). Also, build requirements like compilers that aren't required for the ports operation once installed. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Port upgrade outdated no longer plays nice
On 6/11/12, Jasper Frumau wrote: > On Mon, Jun 11, 2012 at 6:19 PM, Dominik Reichardt > wrote: > >> That just means there was nothing outdated to upgrade at the moment (I >> think this error message could use some fine tuning though). > > I see. Did not know that. Thanks! You can check this by running "port echo outdated". If there isn't any output, you don't have any ports to upgrade, unless you haven't synced with the port tree recently or there was some sort of error that prevented the tree from updating. It'd be nice if selfupdate reported how many ports are upgradeable. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: archive_site_local
On 5/15/12, Ryan Schmidt wrote: > > Sounds like: https://trac.macports.org/ticket/32018 So, is there a way to work around this? Maybe a way to escape the colon? Can you point me to why this is broken? What is it that MacPorts doesn't like about the :port convention? -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: archive_site_local [was: MacPorts 2.1.0 has been released]
On 5/15/12, C D wrote:
>
> Then there might be a bug: following the procedure in
> https://trac.macports.org/wiki/howto/ShareArchives2, I have set up a local
> archive repository, which I access through the URL http://localhost:6227/ .
> When this URL is put into ${prefix}/etc/archive_sites.conf, the port number
> 6227 gets replaced with the port name in the fetch command. E.g.: "port -v
> upgrade openssl" leads to
>
> "---> Attempting to fetch
> openssl-1.0.1c_0+universal.darwin_10.i386-x86_64.tbz2 from
> http://localhostopenssl/openssl";
>
> instead of "[...] from http://localhost:6227/openssl";.
This does, at least initially, sound like a bug, unless there's a new
way to specify the port number.
I haven't upgraded yet, but I should have time later today; when I'll
investigate further. In the mean time, you should be able to serve the
portfiles on port 80 and drop the port number in
archive_site_local.conf
If there isn't a proper way to specify the port number, this should be
reported as a bug ( trac.macports.org ).
--
arno s hautala/-| a...@alum.wpi.edu
pgp b2c9d448
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How remove port info but not installed files?
On 2012-04-18, Murray Eisenberg wrote: > > Indeed, it's space I want to conserve on my relatively small SSD boot drive. > > It's the original MacTeX TeXLive 2011 installation I want to keep -- and > NOT the MacPorts version. > > (Various reasons for that preference, including a very helpful GUI > maintenance utility that's part of MacTeX.) In that case, your best bet is to uninstall the texlive and asymptote ports and either compile it yourself, see if you can get one of the precompiled binaries to work, or install it with homebrew (not recommended; due to how homebrew installs into /usr/local, this could cause problems with your MacPorts install). You could also try altering the Asymptote Portfile to not depend on texlive. I'm not sure how extensive these changes would have to be. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How remove port info but not installed files?
On 2012-04-18, Murray Eisenberg wrote: > > What's the simplest way to get rid of the macports files from texlive > and aysmpotote _WITHOUT_ disturbing the original files from the direct > TeXLive 2011 installation? First off, have you experienced any problems with this setup? Now, you probably don't need to remove anything. Aside from the space on disk, the two prefixes _should_ ignore each other. /usr/local can be a headache if other software tries to link to it instead of the MacPorts provided items, but I think you should be safe with the /usr/local/texlive prefix. If you want to keep asymptote, you'll need to keep the MacPorts provided texlive installation as well. You could probably hack around this by editing the asymptote Portfile so that it does not depend on texlive, but then you may also need to (re?)patch asymptote so that it links to /usr/local/texlive instead of /opt/local. This may be as simple as editing or adding a source path so asymptote knows where to look. In either case, this type of usage isn't exactly supported by MacPorts. You may find others who have performed similar hacks and some help there; I know requests often come up for help in using the system or 3rd party version of some library instead of the MacPorts version. These are usually met with varying degrees of success. With the current MacPorts design, you'd be best off uninstalling TexLive 2011 and using the MacPorts version. This is just for space savings though. Overall, I don't think there should be any compatibility issues in having both on your system. I think MacTex even includes an application for switching which texlive installation to use, and this includes support for selecting the MacPorts version. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Can selfupdate be done incrementally
On Fri, Apr 6, 2012 at 20:02, Tim Johnson wrote: > * O'Dell James [120406 13:21]: >> I have a macports update script and launchd plist that schedules an >> (self)update to run. >> I'd be happy to share if anyone wants them. > Please do. I'd love to see them. > TIA Since we're sharing... I use a weekly launchd task [1] to run a script [2] that updates MacPorts, fetches and builds the outdated ports, removes the old inactive versions, and then signs the port archives. The call to portsign.sh at the end is explained at a the Wiki page on signing ports [2]. Once the Lion buildbot is complete (sounds like soon!) I may switch this to daily and update the script to "archivefetch" and "install" before the current "fetch" and "install". And yes, I'm keeping these scripts under /usr/local/. It's not generally a good idea to put things here when running MacPorts, but I do keep a small number of items in that prefix that I know will not interfere with MacPorts. I do intend to migrate to a different prefix at some point. [1]: https://gist.github.com/2324512 [2]: https://gist.github.com/2324493 [3]: http://trac.macports.org/wiki/howto/ShareArchives2 -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: /usr/local question
On 2012-04-05, Jan Stary wrote: > > (The XXX is where my English fails me. Could a native speaker > put the right verb in please that seems to slip my mind?) > > [...] > > While this could be XXXed off as the user's own error, it is a fact that "written off as" "chalked up to" "dismissed as" -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: A port is clashing with another program installed in /opt that is not a port
On 2012-04-02, Ryan Schmidt wrote: > On Apr 2, 2012, at 08:33, Arno Hautala wrote: > >> The dbus port does supply a "+no_startupitem" variant which should >> skip installing the launchd plist. The launchd task isn't started by >> default anyway and I think I recall that ports that depend on dbus are >> usually intelligent enough to start it on their own if it's not >> running (corrections welcome). I certainly don't recall running into >> any issues with having not started the launchd task. > > There have been tons of reports over the years on the mailing list and in > the issue tracker of problems resulting from users not reading and following > the instructions the dbus port prints out: > > I am not familiar with dbus and don't use software that uses dbus, so I > don't know if it will auto-start these daemons, but I have no reason to > believe it will; if the above steps were not necessary to perform manually, > I doubt the maintainer of the port would have gone to the trouble of adding > the note. That's valid, I was just posting my experience that I don't recall ever actually needing to start dbus before using software that depended on it. Granted, that does not mean than dbus never needs to be started manually or by launchd, just that my anecdotal experience is negative in that regard. It's also entirely possible that the software that I've used that requires dbus doesn't actually need to depend on dbus or even that it uses a component of dbus that doesn't need to be started. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: A port is clashing with another program installed in /opt that is not a port
On 2012-04-02, Jerry wrote: > > Error: Target org.macports.activate returned: Image error: > /Library/LaunchAgents/org.freedesktop.dbus-session.plist already exists and > does not belong to a registered port. Unable to activate port dbus. Use > 'port -f activate dbus' to force the activation. > Error: Failed to install dbus > -- > > I looked at /Library/LaunchAgents/org.freedesktop.dbus-session.plist and > found that it is an alias that points to > > /opt/openmodelica/Library/LaunchAgents/org.freedesktop.dbus-session.plist > > It turns that I had some time back installed Open Modelica using a .mpkg > from a .dmg downloaded from http://openmodelica.org/, so that my /opt at the > upper levels looks like this: > > /opt/local > /opt/openmodelica > > If I take the suggestion by the MacPorts error message above to use 'port -f > activate dbus' will this disturb anything with my Open Modelica > installation? So, the issue isn't that anything is installed into /opt/openmodelica, it's that Open Modelica and MacPorts dbus want to install a launchd plist to the same place. I'm not familiar with Open Modelica, but it sounds like it installed it's own copy of dbus. It's possible that you could force the install without issue, but Open Modelica may be reliant on a specific version of dbus and run into issues when using the version supplied by MacPorts. The dbus port does supply a "+no_startupitem" variant which should skip installing the launchd plist. The launchd task isn't started by default anyway and I think I recall that ports that depend on dbus are usually intelligent enough to start it on their own if it's not running (corrections welcome). I certainly don't recall running into any issues with having not started the launchd task. So, your best bet is to clean dbus and reinstall it with the "+no_startupitem" variant. port clean dbus port install dbus +no_startupitem port install py-spyder It may also be worth while to report this issue to Open Modelica. I doubt that their launchd plist is required for operation. Better Solution: I notice that Open Modelica suggest using MacPorts to install their software. It may be best to remove the /opt/openmodelica directory, the launchd plist that linked to that directory, and any other OM files that you can find, and reinstall using MacPorts. That you have files in /opt/openmodelica, a dbus plist that is linked in a similar way to how MacPorts manages things, and that the developers suggest using MacPorts to manage your installation suggests that the binary release that they've provided was created by a MacPorts installation from a custom prefix. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Xcode 4.3.2 macports requirement (please add to FAQ)
On 2012-04-02, ximon wrote: > Hmmm, > > After upgrading a little while ago to Xcode 4.3.1, I find I am unable to > install the command line tools - an error message is displayed informing me > that my developer account is "not in good standing" and needs to be > updated. I followed the link to the member centre and logged in but there > doesn't seem to be an account update procedure. I updated my profile but > that didn't help either. > > Do I need to join one of the suggested (iOS, Mac or Safari) developer > programs? You shouldn't need to pay for a developer program in order to download the Command Line Tools. I do recall that this was an issue when 4.3.2 was first released, but it seemed to be corrected on Apple's side fairly quickly (I think it was only a few hours). You might try removing / logging out of your Apple ID or Developer ID, log back in, and try again. If you're still seeing the issue you should probably contact Apple's Developer support. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: build/release libraries
On Sat, Mar 31, 2012 at 01:52, Marko Vranic wrote: > > Are mac ports libraries build in debug or in release mode?How can I get both > kind? This is going to be on a port by port basis. Some offer debug as a variant, but most probably are just release. If there's a specific port that you're looking for debug mode and it's not already available, you can probably file a ticket to request this feature. What ports are you interested in? -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: noidle
On Thu, Mar 22, 2012 at 19:05, Ryan Schmidt wrote: > > building something with MacPorts is not being idle. I think this is debatable and would vary from user to user. At the least I'd want a way to disable any noidle behavior. > Note that video players like VLC and Apple's DVD Player probably also > manipulate the power manager so the system doesn't go to sleep in the middle > of a video. I think this is a special case that's not exactly comparable. When watching a video (fullscreen only?) the user shouldn't have to continue to move the mouse so the display doesn't sleep. I can certainly see the argument that a user would expect the compilation task to be considered a noidle event, but it's not a slam dunk in my mind. It would certainly be a nice feature (either through macports.conf or as a flag). That VLC can do this suggests that this behavior shouldn't require sudo to accomplish. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Cleaning up stale dependencies
On Sun, Feb 26, 2012 at 17:21, Ryan Schmidt wrote: > > It works fine for me. > > Perhaps you have +python27 set in your variants.conf? (I don't.) If you do, > then the behavior you see is expected. So I do. Now back to your regularly scheduled programming. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Cleaning up stale dependencies
On Sun, Feb 26, 2012 at 14:38, Ryan Schmidt wrote: > > "port deps inkscape +python26" would show you the deps of inkscape with the > python26 variant, if you were interested in that. FYI, this actually errors out. It seems that port isn't following all of the dependency / variant logic. > $ port deps inkscape +python26 > Error: inkscape: Variant python26 conflicts with python27 > Error: Unable to open port: Error evaluating variants Disabling the conflicting variant was successful. > $ port deps inkscape +python26 -python27 > Full Name: inkscape @0.48.2_2+python26+universal > Build Dependencies: pkgconfig, intltool, perl5 > Library Dependencies: boehmgc, gsl, gtkmm, gnome-vfs, lcms, poppler, boost, > ImageMagick, libwpg, gtkspell2, py26-lxml, py26-numpy, py26-xml -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: audio/sox update
On Tue, Jan 24, 2012 at 12:36, Arno Hautala wrote: >> >> So I don't think ffmpeg brings anything usefull to SoX. >> If anyone is using it successfully, please report. > > I know I have sox installed at home, so I'll check in a few hours. I'm seeing the same behavior here and in searching for those errors I see that you've asked about this on the sox dev-list. I look forward to seeing how this turns out. Thanks for bringing it up. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: audio/sox update
On Tue, Jan 24, 2012 at 12:17, Ryan Schmidt wrote: > > We no longer want to use variants whose names begin with "no_". > > http://trac.macports.org/wiki/PortfileRecipes#default_variants Yep, Jeremy set me straight regarding this in a message that I hadn't realized was off-list. Thanks. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: audio/sox update
2012/1/24 Jan Stary : > > No; dirac only depends on cppunit. > (Why would a video codec depend on a typesetting system?) Yep, as I prefixed my previous message, I'm not at a Mac right now and was basing my statements on my web search. I shouldn't have stopped with a 3 year old bug report though. The issue [1] was resolved by adding a "+doc" variant that excludes many of the dependencies. Similar variants were added to other ffmpeg deps. As Lenore states, it's libsdl that is bringing in x11 and which does have a "+no_x11" variant. [1]: http://trac.macports.org/ticket/18372 > I have looked further into the ffmpeg functionality of SoX; > now I want to remove ffmpeg support altogether. > > [...] > > I tried converting a standard wav into each of these; > none of them actually works. > > [...] > > So I don't think ffmpeg brings anything usefull to SoX. > If anyone is using it successfully, please report. I know I have sox installed at home, so I'll check in a few hours. I wouldn't consider these failing conversions as a reason to remove ffmpeg support though. Rather, if support really is broken, and it's not due to something specific to MacPorts, it should be reported upstream. Regardless, I'm personally not convinced that ffmpeg should be "demoted" to even a default variant. Maybe it's just symantics. In the past MacPorts has always strived to limit the number of variants unless there's a legitimate case for the change. If ffmpeg conversions are failing, they should be fixed. If ffmpeg is bringing in an unwanted x11, the variants are there to reign this in. Then again, I'm just another user. :-) -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: audio/sox update
I'm not in front of a Mac right now so I can't comment on the majority
of these points, however:
On Tue, Jan 24, 2012 at 05:45, Jan Stary wrote:
>
> - drops the dependency on ffmpeg, which in turn depends on the
> whole xorg-* world, thus turning a neat little audio app into
> a monstrous dependency hog; the ffmpeg build is left as a variant
If you do a search for "macports ffmpeg xorg" or "macports ffmpeg x11"
you'll see some discussion on trac about this. The issue is that
ffmpeg depends on dirac which depends on texlive etc. etc. In the end,
variants have already been added to dirac and its deps to disable x11.
I think dropping the default dependency on ffmpeg isn't the right
thing to do here. You can already drop the xorg world by modifying the
variants of ffmpeg deps, so at most I'd think you'd want to add a
variant that removes the ffmpeg dep (+no_ffmpeg).
To save some hassle in managing things on the user end, you can add
"+no_x11" to your ${prefix}/etc/macports/variants.conf
In general, it'd be useful to see your changes as a unified diff (diff
-u) from the current Portfile. It'd also probably be best to file an
issue on trac and then post a message here, to bring it to wider
attention, if you don't see any movement or comments on the trac
issue.
--
arno s hautala /-| a...@alum.wpi.edu
pgp b2c9d448
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: openssh question 2
On Wed, Jan 18, 2012 at 10:43, Brad Allison wrote: > > These are the same type errors I was getting with the default provided sshd > from MacOSX. "Failed to determine Kerberos principal name." errors. Check your Remote Login settings under System Preferences > Sharing > Remote Login Specifically, who is allowed to log in? From: http://think.random-stuff.org/posts/mac-os-x-ssh-quickie via Google -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Perl 5.14 ad default, and Irssi to use it
On Tue, Jan 17, 2012 at 14:06, Daniel J. Luke wrote: > On Jan 16, 2012, at 7:56 PM, Ryan Schmidt wrote: >> Because I was under the impression that cpan would install things to the >> same place that MacPorts would install them, and thus cause a conflict. > > no, it won't (except for maybe may pages and stuff that goes into $prefix/bin) Writing to $prefix/bin would still cause issues. Is there a way to direct cpan to install everything, that would otherwise be placed outside of 'site', to another directory? -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
port issues (was Re: x264transcode failing in mkvtoonix)
On 2012-01-12, Craig Treleaven wrote: > > BTW, would there be any possibility of an enhancement to MacPorts to report > known issues with a port and its dependants? Ie generate the list of > dependencies for a port and query the trac database for any open tickets. > aka > >>port issues mkvtoonix > boost - #32558 (mkvtoolnix: error: 'boost::BOOST_FOREACH' has not been > declared) That sounds like it'd be really useful. Currently, you can do this manually by running "port rdeps mkvtoolnix" and then running a query on trac for each : https://trac.macports.org/report/16?PORT=boost or http://trac.macports.org/query?status=assigned&status=new&status=reopened&port=%7Eboost&summary=%7E&order=priority Being able to combine these in port would be a nice shortcut. You should open a feature request on trac for this. It also might make a good Google Summer of Code project. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: MacPorts-2.0.3 can’t be installed on this computer.
On 2012-01-11, Ryan Schmidt wrote: > > On Jan 11, 2012, at 11:10, Arno Hautala wrote: >> >> It would probably be a good idea to add a note regarding this to the >> uninstall page. > > Already there: Ah, so it is. I was looking lower down on the page. >> And perhaps alter the suggested "rm" command. > > Alter it how? I was thinking have a command that removes everything and also one that removes everything except /opt/local and instead moves that aside. But, as you say, that complicates the instructions. The caveat that I initially missed is probably good enough. Sorry to derail the conversation. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: MacPorts-2.0.3 can’t be installed on this computer.
On 2012-01-11, Bradley Giesbrecht wrote: > > Caution should be exercised if for example you user database file in > /opt/local/var/db/mysql5 or user conf files in /opt/local/etc. > > I would suggest you first move /opt/local out of the way; then after you > have the current MacPorts installed and previous functionality restored you > can delete the old dir. It would probably be a good idea to add a note regarding this to the uninstall page. And perhaps alter the suggested "rm" command. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: MacPorts-2.0.3 can’t be installed on this computer.
On 2012-01-11, Kristen McQuinn wrote: > > I followed the instructions to manually uninstall the files, but no files > were found. Which files did you try to delete? You may indeed not have some of the files / folders that are listed. What commands did you enter in the Terminal to attempt this deletion? > I manually deleted the port, portindex, and portmirror files that I found > in /opt/local/bin. > Then I tried to install the MacPorts-2.0.3 dmg, but got the same error as > before (must install 1.7.1 first). Instead of deleting specific files in /opt/local, you should be deleting /opt/local and its contents, along with the other files and folders listed on the uninstall page. http://guide.macports.org/chunked/installing.macports.uninstalling.html -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How can I control the Perl version I want?
Wouldn't perl need to be installed as "perl5 +perl5_14" not "perl5 @5.14.1_2"? The default is activated by the variant given to the perl5 pseudo port. I think you'd only be able to run "perl5 @" if the specified version had already been built, but was inactive. On 2012-01-05, Ryan Schmidt wrote: > > On Jan 5, 2012, at 12:52, Rodolfo Aramayo wrote: > >> Thanks but the problem is that the port: >> >> perl5 @5.12.3_1+perl5_12 (active) >> >> was installed by another port not by me...I requested: >> perl5.14 @5.14.1_2 > > No problem. Multiple perls can happily coexist. > > >> So I did what you guys suggested and issued the command: >> >> port install perl5 perl5.14 @5.14.1_2+threads >> >> but the "perl --version" port still is: "This is perl 5, version 12, >> subversion 3 (v5.12.3) built for darwin-multi-2level" > > That should not be. /opt/local/bin/perl should now be a simlink to perl5.14. > What does "ls -l /opt/local/bin/perl" and "port installed perl5" show? What > does "which perl" show? > > >> Should I uninstall ALL perls before issuing the command: >> >> port install perl5 perl5.14 @5.14.1_2+threads?? > > No. > > > ___ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Permission Denied with source installation
On Mon, Jan 2, 2012 at 22:31, Lawrence Velázquez wrote: > On Jan 2, 2012, at 10:23 p.m., Arno Hautala wrote: > > Next time you try installing into your home directory, you might want to try > > ./configure --with-no-root-privileges Thanks for the tip. Though I think I recall that some ports have a problem with this. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Permission Denied with source installation
On Mon, Jan 2, 2012 at 20:42, Ryan Schmidt wrote: > > You've installed MacPorts into your home directory, but are still using the > "macports" user, which does not have permission to access things in your home > directory. Either configure MacPorts to use a different user (for example > your user), or (not recommended) give the "macports" user permission to read > your home directory. Yep, while not there yet, I was starting to understand the permissions problem. For now I've simply added a repository to my standard MP install. Thanks for the clarification. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Permission Denied with source installation
First off, I've already tried "port clean". So I'm wondering if it's
an issue specific to how I'm installing from source.
I built and installed v2.0.3 using the following scripts:
src_env.sh
> #!/bin/sh
>
> export MACPORTS=/Users/arno/Code/macports/development/macports
> export PATH=/bin:/sbin:/usr/bin:/usr/sbin
> export PATH=$MACPORTS/bin:$MACPORTS/sbin:$PATH
> export MANPATH=$MACPORTS/share/man
> export EDITOR=/usr/bin/nano
> export LDFLAGS="-L${MACPORTS}/lib"
> export CPPFLAGS="-I${MACPORTS}/include"
> export PKG_CONFIG_PATH=$MACPORTS/lib/pkgconfig
> export LD_LIBRARY_PATH=$MACPORTS/lib
> export LD_RUN_PATH=$MACPORTS/lib
build.sh
> #!/bin/sh
>
> . /Users/arno/Code/macports/util/src_env.sh
> export PATH=/bin:/sbin:/usr/bin:/usr/sbin
>
> ./configure --prefix=/Users/arno/Code/macports/development/macports/
> --with-tclpackage=/Users/arno/Code/macports/development/tcl/
> --with-applications-dir=/Users/arno/Code/macports/development/Applications/
> --with-frameworks-dir=/Users/arno/Code/macports/development/Frameworks/
> --with-ports-dir=/Users/arno/Code/macports/development/ports/
> make
> echo
> echo now \"sudo make install\"
I then run "sudo make install", source src_env.sh, and run a selfupdate.
And that's where I start seeing the permission problems on any
installation actions (pasted below). It does indeed seem like it's the
issue that should be cleared up by a "port clean", but I'm seeing the
same behavior after that.
Any ideas or additional information that I can provide?
Thanks for your help.
> $ sudo port -d fetch bash-completion
> DEBUG: Changing to port directory:
> /Users/arno/Code/macports/development/macports/var/macports/sources/rsync.macports.org/release/tarballs/ports/sysutils/bash-completion
> DEBUG: OS darwin/11.2.0 (Mac OS X 10.7) arch i386
> DEBUG: org.macports.load registered provides 'load', a pre-existing
> procedure. Target override will not be provided
> DEBUG: org.macports.unload registered provides 'unload', a pre-existing
> procedure. Target override will not be provided
> DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing
> procedure. Target override will not be provided
> DEBUG: only one arch supported, so not adding the default universal variant
> DEBUG: Attempting ln -sf
> /Users/arno/Code/macports/development/macports/var/macports/build/_Users_arno_Code_macports_development_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_bash-completion/bash-completion/work
>
> /Users/arno/Code/macports/development/macports/var/macports/sources/rsync.macports.org/release/tarballs/ports/sysutils/bash-completion/work
> DEBUG: changing euid/egid - current euid: 0 - current egid: 0
> DEBUG: egid changed to: 501
> DEBUG: euid changed to: 503
> DEBUG: couldn't open
> "/Users/arno/Code/macports/development/macports/var/macports/build/_Users_arno_Code_macports_development_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_bash-completion/bash-completion/work/.macports.bash-completion.state":
> permission denied
> while executing
> "open $statefile a+"
> (procedure "open_statefile" line 63)
> invoked from within
> "open_statefile"
> (procedure "check_variants" line 29)
> invoked from within
> "check_variants fetch"
> invoked from within
> "$workername eval check_variants $target"
> (procedure "mportexec" line 7)
> invoked from within
> "mportexec $workername $target"
> Error: Unable to execute port: couldn't open
> "/Users/arno/Code/macports/development/macports/var/macports/build/_Users_arno_Code_macports_development_macports_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_bash-completion/bash-completion/work/.macports.bash-completion.state":
> permission denied
> To report a bug, see
--
arno s hautala /-| a...@alum.wpi.edu
pgp b2c9d448
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gmail phishing warnings
On Thu, Dec 22, 2011 at 11:22, Scott Webster wrote: > On Thu, Dec 22, 2011 at 11:17 AM, Phil Dobbin wrote: >> >> No. Nothing has been flagged about Mac Ports... > > Well, that is weird. Every time you send a message to the list I get > the big warning telling me you are trying to phish me. It isn't just > me who sees this... Using the web interface for Gmail, I'm not seeing any warning about Phil's messages (and I don't recall seeing this recently on other messages). Is there a way to disable this warning that I, and others, may have set in Gmail? Though, the alum.wpi address that I use forwards everything to my Gmail account. Looking at the message source seems to indicate that WPI is adding their own SPF and DKIM information. I wonder if that's a flaw or if there's an exception that recognizes list mail or MacPorts specifically. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: [SPF:Probably_Forged] Re: Missing updated features?
On Wed, Dec 14, 2011 at 13:12, Adam Dershowitz wrote: > > At this point my ports are up to date. You could always uninstall, clean, and reinstall a small port to test. bash-completion would be a good option I think. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Missing updated features?
On Wed, Dec 14, 2011 at 12:11, Adam Dershowitz wrote: > One is that I still need sudo to run all my macports commands. I believe > that this should no longer be necessary. > Does doing a selfupdate not create the new macport user? Does that have to > be done manually or some other way? If you've upgraded and aren't seeing any build errors, this feature is probably working just fine. The macports user is used for building, but root is still necessary for the activation of a port when the files are moved into place. There are other discussions about not requiring sudo to build and install, but those are regarding non-standard installations. > Two is that I am using OS 10.6.8, yet I have never seen a binary download. I > still always download source and then it builds. This should indeed be the default. Can you post a transcript a port installation? It's possible that the ports that you've installed aren't available as pre-compiled binaries (licensing, variants, etc). There should be a status line that states that port is trying to fetch the binary from http://packages.macports.org/ You can browse that page to verify that the port you're installing should be available. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Macports 2.0.3/Lion 10.7.2 Perl
On Wed, Nov 2, 2011 at 12:45, Arno Hautala wrote: > > Hmm, I was writing this from memory and I'm not at my Mac right now. > Maybe there isn't a perl group? I'll write back when I'm in front of > my machine and can check. Yep, turns out you don't use select for perl. Instead, install the 'perl5' port with the desired version as a requested variant. It's possible to install a perl version directly, but you won't get the non-suffixed command installed. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Macports 2.0.3/Lion 10.7.2 Perl
On Wed, Nov 2, 2011 at 12:11, Mr. Puneet Kishor wrote: > > I had no idea... thanks for the above info. Now then, what is going on here? > > $port select --list perl > Warning: Unable to get active selected version: The specified group 'perl' > does not exist. > Error: The 'list' command failed: The specified group 'perl' does not exist. Hmm, I was writing this from memory and I'm not at my Mac right now. Maybe there isn't a perl group? I'll write back when I'm in front of my machine and can check. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Macports 2.0.3/Lion 10.7.2 Perl
On Wed, Nov 2, 2011 at 10:39, Jason Lixfeld wrote: > > 1. Is it normal for Macports to not use system Perl in this manner, or at > least add to @INC to point to the module directories installed via ports? Yes, MacPorts, for the most part, selects to install its own software rather than relying on the system. The primary reason for this is maintaining compatibility in the event that the system changes the installed version of a tool that breaks compatibility with an old version. > 2. Is it normal for Macports to not create a symlink to perl in > /opt/local/bin You can set this using "port select". "port select --list perl" "port select --show perl" "port select --set perl " > 3. For some reason when I add #!/opt/local/bin/perl5.12 to the top of a perl > script (that had otherwise been working for years), I get an error thrown: > > BlackBox:Scripts jlixfeld$ ./csv-parser.pl > -bash: ./csv-parser.pl: /opt/local/bin/perl5.12^M: bad interpreter: No such > file or directory > > BlackBox:Scripts jlixfeld$ /opt/local/bin/perl5.12 csv-parser.pl That "^M" is the issue. Try running "dos2unix" (also available in MacPorts) on the file and run it again. The shell is interpreting the line ending as part of the path. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: how to install old port subversion in tbz2?
On Mon, Oct 17, 2011 at 14:54, Ryan Schmidt wrote: > > Then again nobody has publicly announced anything at all about archives yet, > not even their existence. I have to say it seems just a little bit odd that MacPorts now will try to install ports by downloading pre-compiled archives, but an announcement of this behavior has not been made. Maybe it's just me, but I get a fuzzy weird feeling about that, and I know that it's doing this. Again, maybe it's just me. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: iTerm2 does not start up on mac lion
On Sat, Oct 8, 2011 at 14:01, Tim Johnson wrote: > I installed iTerm2 with macports. Installation showed no errors and > no notes were available that I could see. > > When I attempt to start iTerm2, I get an icon on the dock, but it does > not open. Any ideas about what I may have done wrong? I just installed it here and I see the same behavior. I can get other windows, like Preferences, but no terminal windows. I'd try to download a beta if it's available and then file a bug either with MacPorts or upstream depending on how the beta functions. Interesting that MacPorts has the version set at 1.0.0, but I'm pretty sure the iTerm app reported 1.1b or something. Maybe the SVN tag is screwed up. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Can't install - 'Xcode is not installed..'
On Tue, Oct 4, 2011 at 02:48, Dominik Reichardt wrote: > > It's Apples fault for not taking care of this expectations mismatch, they > should just initiate the installer after download (or give some dialog that > this is just the installer and it needs to be run first). I think this is an area where MacPorts is exposing a niche bug. Most users who download Xcode from the Mac App Store are going to want to run it immediately or somewhat soon. They'll quickly realize that only an installer has been downloaded and they still need to run that in order to use Xcode. MacPorts users likely represent a decent pool of users who simply want Xcode in order to run MacPorts and think downloading from the store is all that they need to do; everything else downloaded from the MAS works that way. While it'd be nice if Apple already notified users, I wouldn't be surprised if they saw it as an unnecessary effort. Checking for the installer would be a nice touch on MacPorts' part. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: moving macports to a different location
On Tue, Sep 13, 2011 at 11:54, Puneet Kishor wrote: > I was hoping to simply copy the /opt tree to the new computer. However, the > iMac has two disks, and I want to set up macports on /Volumes/extradrive/opt. > My question -- can I, should I do this, and how? You could certainly copy the full file tree to the new location and then edit etc/macports/macports.conf to update the relevant paths. One issue that I could see croping up is if there are any absolute paths that have been compiled into installed software. I'll leave it to someone else to comment there. I'm sure this isn't a supported process. > If not, is there an easy way I can recreate all the packages from my MBA on > to my iMac without having to install each one separately? I was going to suggest installing from the software archives that exist on the MBA, but MacPorts always compiles from source if you're using a non-standard prefix. Why do you want to use the extra drive for MacPorts? There may be a better solution than what you're asking for. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: What is db46 and why is it such a pain?
On Thu, Sep 8, 2011 at 10:16, wrote: > > How do I actually do the renaming? Copy the failing files from /opt/local/var/macports/distfiles/db46/ to some other location (maybe your Desktop). Use the Finder to add ".html" to the end of each file you're going to check and drag each into your browser. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: What is db46 and why is it such a pain?
On Thu, Sep 8, 2011 at 07:09, Yves S. Garret wrote: > > I meant ask you guys, what do you mean by this: > > > Try renaming the downloaded patch files to have a .html extension and > > loading them in a browser. One of the possibilities when the patches fail the checksum is that the download has been redirected to an error page, a license agreement, or some other resource. MacPorts has retrieved whatever this redirect is and named it according to what the patch *should* have been named if the download was successful. In this case, you might gain insight into what went wrong by renaming the downloaded file with a ".html" extension and attempting to open it with a web browser, or even a text editor. If for example, the direct download had been redirected to a license agreement, opening the file in a browser may display that agreement and indicate how to restore the direct download. Or an improperly served 404 page could indicate that the patch had been removed and might even indicate where to find the replacement. Or it might indicate a temporary failure and may offer a hint towards handling such misbehaving servers in the future. It's basically another debugging step that could provide additional information if the problem had persisted. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Active version error
On Sun, Aug 21, 2011 at 05:42, Frank J. R. Hanstick wrote: > Hello, > The following occurred during an upgrade: > > [snip] > > ---> Activating p5.12-scalar-list-utils @1.230.0_2 > Error: Target org.macports.deactivate returned: Active version of > p5-scalar-list-utils is not 1.230.0_1 but 1.23_1. > Log for p5-scalar-list-utils is at: > /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_p5-scalar-list-utils_1.23_1/p5-scalar-list-utils/main.log > Warning: Failed to execute portfile from registry for p5-scalar-list-utils > @1.23_1 > ---> Deactivating p5-scalar-list-utils @1.23_1 > ---> Cleaning p5.12-scalar-list-utils > > This was not a show stopper. A log is attached. It's a bug in the Perl 5 PortGroup. I'm looking at in now and have figured out where the issue occurs, but I'm not sure of the correct solution as I'm unfamiliar with _why_ the version string is being manipulated. It's being tracked at https://trac.macports.org/ticket/30833 -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: macports install fails on lion
On Thu, Aug 11, 2011 at 10:35, wrote: > > on Lion, i installed xcode 4 for Lion > from the connect.apple.com. Are you sure that you installed Xcode 4 from connect.apple.com? I thought it was only available from the Mac App Store. If you did actually install from the Mac App Store, did you actually install by running the Xcode installer? Or perhaps you just downloaded the installer. You'll have to manually run the Xcode installer that is located in your Applications folder. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Multiple archive_site_local configurations?
Is it possible to list multiple archive_site_local values? I don't currently have the assets to test such an arrangement or I'd have simply tried it out. This is more of a hypothetical. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Sharing port archives
On Fri, Jul 29, 2011 at 05:40, Matthias Pigulla wrote: > > does https://trac.macports.org/wiki/howto/ShareArchives still apply after > https://trac.macports.org/ticket/19458 has been closed? Looking at the history for the Wiki page, I think you've figured out your answer. > How can compiled ports be shared between machines (e. g. by placing them on a > network share) in MacPorts 2.0.0? I'm not sure about a network share (do you mean something like a NAS device? or just from another machine?), but I did get archive sharing to work by publishing the software directory with lighttpd. I also put together a shell script, based on the one Josh pointed me to, that signs every archive. Unless someone gets to it first, I'll put up a HowTo on this tonight or tomorrow. It's fairly simple. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port fetch archives?
Excellent. Thanks. On Tue, Jul 26, 2011 at 06:18, Rainer Müller wrote: > > Yes, it is called 'port archivefetch'. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
port fetch archives?
I've successfully enabled fetching archives from my desktop installation (Thanks!). Now, I wonder if there is an equivalent command to fetch those archives as there is to fetch the source package. I can already run something like "port fetch outdated" in order to grab all the source packages that need to be built prior and it'd be nice to be able to do the same when simply installing from precompiled binaries. Is there such a command or option? -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
