Why oxygen-icons port requires qt4-mac & phonon?
Why do the oxygen-icons actually require ports qt4-mac and phonon installed? --- $ port deps oxygen-icons Full Name: oxygen-icons @4.12.5_0 Extract Dependencies: xz Build Dependencies: cmake, pkgconfig, automoc Library Dependencies: qt4-mac, phonon --- ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Permissions change with MacPorts 2.3?
At 11:02 PM +0200 6/3/14, Clemens Lang wrote:
Hi,
I sometimes use EasyFind to search in portfiles. I noticed today
that the macports folder under ${prefix}/var is no longer visible. I
would guess this happened after I upgraded to MacPorts 2.3 but I
can't be certain. Using the command line, I see the following:
[]
Was it an intended change to hide this directory? Or a glitch on my system?
That was intentional. In specific, it's this Changelog entry:
Disable Spotlight indexing on build directories, distfiles,
registry, log files, archives, base source and the default ports
tree. (cal in r113649)
You can avoid this by manually reverting the change and touching a file
named ".nohide" in the directory. See
http://trac.macports.org/changeset/113649
Thanks. I noticed that in the change log but
didn't see how it was implemented.
Based on some searching (ie no hands-on
experience!), it seems that it might be simpler
to create a ".metadata_never_index" file [1]
inside that folder to encourage Spotlight to
leave it alone. Alternatively, we could add
".noindex" to the folder name to achieve the same
effect.
Wouldn't one of these be a better solution?
Craig
[1]
http://apple.stackexchange.com/questions/92784/preventing-spotlight-from-indexing-files-folders
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Permissions change with MacPorts 2.3?
Hi,
> I sometimes use EasyFind to search in portfiles. I noticed today
> that the macports folder under ${prefix}/var is no longer visible. I
> would guess this happened after I upgraded to MacPorts 2.3 but I
> can't be certain. Using the command line, I see the following:
> […]
> Was it an intended change to hide this directory? Or a glitch on my system?
That was intentional. In specific, it's this Changelog entry:
Disable Spotlight indexing on build directories, distfiles,
registry, log files, archives, base source and the default ports
tree. (cal in r113649)
You can avoid this by manually reverting the change and touching a file
named ".nohide" in the directory. See
http://trac.macports.org/changeset/113649
HTH,
--
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: "ticket" port command?!
Just realized that I forgot to make sure that this made it back to the lists, so re-cc-ing macports-dev... On Mon, May 12, 2014 at 3:23 AM, wrote: > Hi Eric, > > On 12 May 2014, at 01:40 , Eric Gallager wrote: > > Yes, it would be... I came across a script that did the querying and > > viewing parts before, so I added it to my macportsscripts repo: > > > https://github.com/cooljeanius/macportsscripts/blob/master/macportstrac.sh > thanks for the link. > > > (the macportsscripts port should install it) > Oh, I didn’t know it even exists as a port. :) > > > But yeah, that script is really rudimentary and stuff, and it would be > > much better to have the sort of functionality you were describing in > > base instead of in some random script. > As Brad wrote, this is all about viewing, but as I suggested the > pre-filling > of a new ticket form as well as uploading of the often asked for main.log > would be a valuable addition to it, which is why it should be part of > port’s TCL code base, I believe. > > But I’ll install your port as well as Brad’s scripts this evening. > > Greets, > Marko > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: "ticket" port command?!
On Tue, May 20, 2014 at 5:21 PM, Bradley Giesbrecht wrote: > There is the macportsscripts port, I don't know much about it > The macportsscripts port used to be phw's, and installed a single script, port-fetchall.sh, that dealt with the issue described in < https://trac.macports.org/ticket/2421>. I took it over after forking it and adding a bunch of new scripts to it: https://trac.macports.org/ticket/37836 Since then I have updated the port 3 more times: https://trac.macports.org/ticket/38432 https://trac.macports.org/ticket/39117 https://trac.macports.org/ticket/41788 Most of the scripts in it are just ones that I have found on Trac or elsewhere around the internet, but I have modified them and stuff. If you find other scripts elsewhere that you would like added to the repo, just send me a pull request or let me know some other way or something. > > In users/pixilla/scripts I have prefixed my commands/scripts with "mp-" > which I like because I can type "mp-" and hit tab a couple times to see > what commands I have available to me. I try to mimic what the command does > in the name like "mp-svn-up-dports". Where the name ends with port, like > "mp-svn-log-port" we run "svn log" on whatever "port" makes of our input. > example: > mp-svn-log-port maintainer:g5pw > > > Regards, > Bradley Giesbrecht (pixilla) > > On May 20, 2014, at 4:29 AM, Aljaž 'g5pw' Srebrnič > wrote: > > Thanks for the links, Bradley. > > > > I was thinking that it would probably be nice to have a common set of > utilities like there to ease portfile development. What do you guys think? > > > > > > On 19 maggio 2014 at 19:28:27, Bradley Giesbrecht (pixi...@macports.org) > wrote: > >> On May 13, 2014, at 12:53 AM, Aljaž Srebrnič wrote: > >> > >> > >> This may be the script Ryan uses: > >> http://trac.macports.org/browser/users/ryandesign/scripts/portissues > >> > >> I use this script: > >> > http://trac.macports.org/browser/users/pixilla/scripts/mp-trac-tickets-port > >> > >> mp-trac-tickets-port name:^dovecot2 > >> > >> > >> Regards, > >> Bradley Giesbrecht (pixilla) > >> > >> > >> ___ > >> macports-dev mailing list > >> macports-dev@lists.macosforge.org > >> https://lists.macosforge.org/mailman/listinfo/macports-dev > >> > > > > ___ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev > > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Permissions change with MacPorts 2.3?
Hi:
I sometimes use EasyFind to search in portfiles. I noticed today
that the macports folder under ${prefix}/var is no longer visible. I
would guess this happened after I upgraded to MacPorts 2.3 but I
can't be certain. Using the command line, I see the following:
CT-MBP11:~ craigtreleaven$ ls -@al /opt/local/var/
total 0
drwxr-xr-x 12 root admin 408 10 Feb 10:44 .
drwxr-xr-x 15 root admin 510 10 Dec 17:22 ..
drwxr-xr-x 3 root admin 102 29 May 2012 cache
drwxr-xr-x 5 root admin 170 22 Mar 16:56 db
drwxr-xr-x 5 root admin 170 19 Nov 2013 lib
drwxr-xr-x 7 root admin 238 21 Apr 14:20 log
drwxr-xr-x@ 13 root admin 442 27 May 16:11 macports
com.apple.FinderInfo 32
drwxr-xr-x 4 root admin 136 29 May 09:49 mythtvuser
drwxr-xr-x 3 root admin 102 10 Feb 10:44 openldap-data
drwxr-xr-x 3 root admin 102 10 Feb 10:44 pwcheck
drwxr-xr-x 9 root admin 306 29 May 09:49 run
drwxr-xr-x 3 root admin 102 10 Feb 10:44 state
CT-MBP11:~ craigtreleaven$ xattr -v /opt/local/var/macports
/opt/local/var/macports: com.apple.FinderInfo
Was it an intended change to hide this directory? Or a glitch on my system?
Craig
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac is down (eom)
Hi All Trac is now up again. Let me know if you see any issues. Shree On Jun 3, 2014, at 8:38 AM, Christoph Iserlohn wrote: > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
trac is down (eom)
___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [120476] trunk/dports/cross/avrdude/Portfile
Thanks for the info! I wasn’t sure so i revbumped anyway.
On 29 maggio 2014 at 23:01:39, Ryan Schmidt (ryandes...@macports.org) wrote:
> On May 29, 2014, at 10:22 AM, g...@macports.org wrote:
>
> > Revision
> > 120476
> > Author
> > g...@macports.org
> > Date
> > 2014-05-29 08:22:23 -0700 (Thu, 29 May 2014)
> > Log Message
> >
> > cross/avrdude:
> > docs require latex to be present, so adding texlive ad a build dependency,
> > and making the variant optional
> >
> > Modified Paths
> >
> > • trunk/dports/cross/avrdude/Portfile
> > Diff
> >
> > Modified: trunk/dports/cross/avrdude/Portfile (120475 => 120476)
> >
> > --- trunk/dports/cross/avrdude/Portfile 2014-05-29 15:13:37 UTC (rev
> > 120475)
> > +++ trunk/dports/cross/avrdude/Portfile 2014-05-29 15:22:23 UTC (rev
> > 120476)
> >
> > @@ -5,6 +5,7 @@
> >
> >
> >
> > name avrdude
> >
> > version 6.1
> >
> > +revision 1
> >
> > categories cross devel
> >
> > maintainers bdmicro.com:bsd
> >
> > description an Atmel AVR MCU programmer
> >
> > @@ -29,10 +30,8 @@
> >
> > configure.args --mandir=${prefix}/share/man \
> >
> > --disable-parport
> >
> >
> >
> > -variant docs description {Build documentation} {
> > - depends_build-append port:texinfo
> >
> > +variant docs description {Build documentation (requires LaTeX)} {
> > + depends_build-append port:texlive
> >
> >
> >
> > configure.args-append --enable-doc
> >
> > }
> >
> > -
> > -default_variants +docs
>
> There is no reason to revbump when removing default variants, because
> MacPorts will
> not remove variants from an installed port unless the user explicitly tells
> it to do so
> (e.g. by using "sudo port upgrade --enforce-variants avrdude -docs")
>
>
>
>
>
--
Aljaž 'g5pw' Srebrnič
Sent with Airmail
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
