> if ‘exp’ is the expression you’re looking for (e.g. ‘%qt4%’ for all files
> containing …qt4…)
>
> sqlite> WITH i AS (SELECT id FROM files WHERE path LIKE exp GROUP BY id)
> SELECT name FROM ports, i WHERE ports.id = i.id;
>
> Assuming you want the name of the ports which provides the files
sqlite3 register.db
if ‘exp’ is the expression you’re looking for (e.g. ‘%qt4%’ for all files
containing …qt4…)
sqlite> WITH i AS (SELECT id FROM files WHERE path LIKE exp GROUP BY id) SELECT
name FROM ports, i WHERE ports.id = i.id;
Assuming you want the name of the ports which provides the
>
> You should check with the developers of Coda on their Git support. I
> don't think a tool built especially for website editing will be the best
> choice, but maybe it works for you.
Otherwise I also use PyCharm free edition for some Python related tasks, and it
seems to have built-in GitHub
Guys,
I’ve bought Coda 2 when I use to do a bit of HTML development. Can I use it to
check out - tinker with the new MacPorts GIT repository?
TIA,
Vincent
___
macports-dev mailing list
macports-dev@lists.macosforge.org
> On 20 Oct 2016, at 21:12, Lawrence Velázquez wrote:
>>
>> Yeah, I get that, but I mean: so nothing has changed yet: SVN is still
>> supposed to work the way it always did (at least to my knowledge).
>
> Right.
Thanks! I get out of your hair.
V.
Hey,
> On 20 Oct 2016, at 14:04, Ryan Schmidt wrote:
>
>> On Oct 20, 2016, at 6:48 AM, Peter Danecek wrote:
>>
>> Hi all,
>> I am current not able to reach the trac server. Is this a real issue, or
>> just a local problem here?
>
> Trac, svn,
Hi Josh!
> On 13 mai 2016, at 16:30, Joshua Root wrote:
>
> As the comment in the quartz variant in the portfile says:
> # tk.h still includes and uses types from X11/Xlib.h
Yep, but I commented the line below, and it compiled fine. So this comment must
somehow be outdated.
Hi there,
why does tk +quartz -x11 depend on libX11? I commented out that line in the
Portfile and it compiled fine.
Leaving that (dangling) dependency alive means installing a lot of cruft.
Cheers!
Vincent
___
macports-dev mailing list
>> I was under the impression that Apple already compressed the files and
>> programs installed with the operating system, using HFS compression, ever
>> since taking up less disk space was listed as a feature of Snow Leopard.
> Yeah, I thought so too, but I also have the impression that may not
> This typically doesn't take a lot of space, and no compiler option will
> remove the unused code in software that was meant to support different CPUs
> at runtime…
Except that you can use configure to detect what model of processor you’re
running on, and then with a -D flag eliminate all the
> Sure. And it is probably also very easy to introduce regressions that way if
> the #ifdefs aren't already in place.
Yeah, that’s right. Every cloud has its silver lining. Or the contrary for that
matter.
> It'll do the same with your /Applications directory or the entire /opt/local
> tree.
Hi René,
> Any MKV file? What VLC version?
Latest one:
port installed | grep VLC
VLC @2.1.5_7+mod+mpc+osd+qtkit+quartz (active)
> What does the VLC log tell you (either in-app or by launching the app bundle
> executable directly from a terminal, with the -vvv argument)?
You will find the
Hi there,
I’ve a strange problem with VLC. Clicking on a MKV file will not crash the app,
but it will go into a sort of infinite loop, as if it was not finding anything
to play inside the file and kept on trying again.
ffplay with the same file works fine, though, so this is not a library
>
> That's indeed that latest one provided through MacPorts, but not the latest
> VLC version. I've submitted a port for 2.2.1 on Trac months ago, but it has
> never been committed.
There’s a “beta” 2.2.2-20150427_3 available on MacPorts, I’ll try it and let
you know.
> Might I suggest that
> Ah, not mine AFAIK. The portfile I submitted on Trac *probably* contains a
> VLC-devel port for 3.0.0-150503-g7385062d (my local copy does), but I don't
> think I tried building or using that one since May last year (1505).
I could have a stab at compiling it, if you want.
> If you only
René,
I compiled VLC 2.2.1 using Macports and still have the same error :(
Seems something is wrong in the MacPorts librairies, but where?
Cheers!
—
VLC media player 2.2.2 Weatherwax (revision 2.2.1-21-g2502874)
[7f9f92f00378] core libvlc debug: VLC media player - 2.2.2 Weatherwax
> You might want to look at the following to clean up those libraries:
>
> $ port info port_cutleaves
[…]
Thanks Craig!
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Craig:
> Do other mkv files play OK?
I haven’t many MKV files, all from the same source, and none plays correctly on
VLC.
FFPLAY has no difficulty reading them.
Strange.
Output of mediainfo:
> mediainfo /Volumes/Archives/Vidéos/Series/MLP\ FIM\ S4/YP-7Z-04x02.mkv
General
Unique ID
> We have a 366x140 version:
>https://www.macports.org/img/macports-logo-top.png
> but that doesn't change anything: we still need a vector version.
Doesn’t inkscape have a vectoriser module?
Vincent
___
macports-dev mailing list
> I tried a couple of options (such as WhatTheFont.com), but no exact match.
> When looking for the font, look for the uncommon capital M and the slight
> bulge on the top of the capital P.
Best way is to vectorise it as paths.
V.
___
macports-dev
SVG version. It might need to have the font loaded, though. What we can do is
transform the letters into paths.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Hi Mojka,
here is a version where the letters have been transformed in paths, so one may
adjust the letters individually.
I’m not sure I’m going to have much time to do the small trimming you talk
about. Will try to have a stab at it, though.
Vincent
> On 27 Nov 2015, at 19:43, Brandon Allbery wrote:
>
> Reinstall from the installer for that platform, yes.
Okay, that’s what I suspected.
Thanks and 73s Brandon.
Vincent
___
macports-dev mailing list
Folks,
I really feel self-conscious to ask that, because I’m sure you’ve already been
flaked with such questions a couple of month ago, but since trac is down…
I’ve been upgrading one of my boxes to 10.11. Unfortunate idea, since I can’t
use “port” anymore, being greeted with an aggressive
> I can only tell you that due to high memory use, the system started killing
> processes to free memory; that apparently included the web server and the ssh
> server. I don’t know what caused the high memory use.
Thanks Ryan!
Have a great day!
Vincent
Hi Mojca,
> I'm not sure what the relation between Scite and QScintilla is.
Well, I’m not sure either, except that the spellchecker of my iPhone wants to
substitute Scintilla by Scite, I guess.
And it is doggedly fixed on that. :(
> Is http://foicica.com/scintillua/README.html compatible with
Folks,
I’ve been able to patch the Portfiles for QScintilla and Qwt and get something
useable with Qt5.
If you’re interested in getting a copy of these, please let me know.
Vincent
___
macports-dev mailing list
macports-dev@lists.macosforge.org
Ryan,
> qt_archdata_dir should be set in the qt5 1.0 portgroup. Do you perhaps have
> local modifications to this portgroup that are conflicting with the official
> version?
Bullseye! But if I delete my qt5-1.0.tcl file and try to recreate it with SVN,
I get this:
> svn update
Updating '.':
On 23 Nov 2015, at 20:49, David Strubbe wrote:
>
> Do 'svn revert' on it.
Thanks! I’m really a noob when it comes to svn use.
Vincent
___
macports-dev mailing list
macports-dev@lists.macosforge.org
Folks,
every time I update my tree from svn I get this message:
“Failed to parse file aqua/qt5/Portfile with subport 'qt5-qtbase': can't read
"qt_archdata_dir": no such variable”
And of course I cannot build Qt5. Has someone a clue?
Thanks,
Vincent
Ryan,
> 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
Folks,
I’m trying to migrate Macports properly rebuilding base, but something fails:
Air > sudo make install
===> making install in vendor
===> making install in vendor/tcl8.5.15/unix
Installing libtcl8.5.dylib to /opt/local/libexec/macports/lib/
Installing tclsh as
Rainer:
>> Bang on. I keep as little archives as possible, because my SSD is cramped (I
>> have a 128 MB version) and I don’t want to cram it with files I seldom if
>> ever use.
>
> I really hope you actually got 128 GB ;-)
Oops. Well… You know, back in the ‘80s, I clearly remember a
Guys,
I haven’t been much active lately and I apologise. I’d a tough September, and,
I own up, procrastinated a bit knowing that 10.11 was about to be released.
Will resume normal activity as soon as I get over the whole migration shebang.
Thanks for your patience!
Vincent
On 21 Jul 2015, at 19:27, Daniel J. Luke dl...@geeklair.net wrote:
IIRC oracle changed the bdb license after 4.6. I have a dim recollection that
I was going to try to look over the new license to make sure it was
reasonable to update the bdb that apr-util (and subversion) use, but I never
On 21 Jul 2015, at 16:02, Brandon Allbery allber...@gmail.com wrote:
On Tue, Jul 21, 2015 at 10:00 AM, Clemens Lang c...@macports.org wrote:
- On 21 Jul, 2015, at 15:43, Rainer Müller rai...@macports.org wrote:
And even if the default +db* variant selection depends on the local
Hi there,
I recently had a look on the smörgåsbord of ports installed on my computer, and
I found out three different versions of db: db44 db46 db48. Turns out a lot of
ports have a fixed dependency on one of the db* ports, which in turn implies
that a lot of different versions of db4 have to
On 18 May 2015, at 05:42, MacPorts nore...@macports.org wrote:
#43758: eero-devel @3.2.2012-11-18: Cannot stat:
.../lang/eero-devel/files/llvm-
bin, No such file or directory
---+-
Reporter: ryandesign@… | Owner: vince@…
Type:
Ryan,
On 01 Jun 2015, at 19:24, Ryan Schmidt ryandes...@macports.org wrote:
master_siteshttps://gforge.inria.fr/frs/download.php/file/34705/
Thanks. Done in r136973. Sorry for the flub.
Vincent
___
macports-dev mailing list
Ryan,
I fixed the description of this variant in r134805.
Thanks. I stupidly did a copy/paste of the postgresql93 variant and overlooked
some changes.
-if {![variant_isset postgresql90] ![variant_isset postgresql91] \
-![variant_isset postgresql92] ![variant_isset postgresql93]} {
Ryan,
in r129787; and in p5-dbd-pg in r130008. postgis2, py-psycopg2 and qgis
remain on postgresql93.
Besides, it lets a bit of time for the apps to accommodate the new version.
I don't recall any compatibility problems ever arising. Do you?
PostGIS is an extension to PostGreSQL and as
Hi there,
I’m conducting a preliminary survey to switch QGis from Qt4 to Qt5.
However, said change would need QWT 6 to be linked against Qt5, which appears
not to be case currently. I picked up on some QGis thread that QWT 6 was
compatible with Qt5, which was not the case with the prior
-master_siteshttps://gforge.inria.fr/frs/download.php/34150
+master_sites
https://gforge.inria.fr/frs/download.php/file/34403/CGAL-4.5.1.tar.bz2
master_sites should be the directory the distfile is in, and should not
include the actual distfile name.
master_sites
Hi Ryan,
/opt/local/Library/Frameworks should not be hardcoded here. Are you sure
commenting out the reinplace is correct?
Will change the hardcoded path. Thanks for pointing that out.
Yes, surprisingly it seems something has changed in the configure script
between 2.1.3 and 2.1.4. With the
Guys,
I am in a middle of upgrading boost, but the old version seems to be a die-hard:
[…]
a
./opt/local/include/boost/accumulators/framework/accumulators/reference_accumulator.hpp
a
./opt/local/include/boost/accumulators/framework/accumulators/value_accumulator.hpp
--- Cleaning boost
---
Hi Chris,
wait longer. It will take a while but will eventually finish…
Yep, it did. Thanks. But that’s really unexpected, especially since I run a MBA
with those super-fast PCI-e SSD.
I think we ought even to warn the user about this (but I don’t think it’s
possible).
Vincent
Le 10 nov. 2014 à 10:55, Chris Jones jon...@hep.phy.cam.ac.uk a écrit :
Are you running OSX 10.10 ? If so its a new issue there, somethings like this
are taking a lot longer than before. I guess idea is to fix it rather than
live with it with warnings, once someone figures out what is
Hi!
Nope, the number of files was pretty much the same on Mavericks, as was the
number of dependents. For some reason, the performance of our SQLite database
plummeted on 10.10; we don't know why.
Caching issue?
V.
___
macports-dev mailing list
Ciao Petr,
I'd like to propose to start commit messages with the port name. This helps
very much to read them for example in the Timeline.
For example:
https://trac.macports.org/changeset/127794 -- Correct various bugs. Bump to
revision 1.
https://trac.macports.org/changeset/127795 --
Guys,
I’m writing an updating port for the new version of gis/gdal.
However, the port does not compile because a .h file installed by the old
version into ${prefix}/include masks a new version of the same .h bundled with
the newest source.
So question 1: is there a standard workaround to
Le 24 août 2014 à 18:53, Sean Farley s...@macports.org a écrit :
Why not use the bitbucket port group?
PortGroup bitbucket 1.0
bitbucket.setup petebunting rsgislib 52fb22e
version 0.0.20140822
Uh, I tried that and it works (fetch okay), but then I have a problem.
Le 25 août 2014 à 20:07, Sean Farley s...@macports.org a écrit :
There are a few ways to work around this. In the dolfin port, I do:
configure.dir ${worksrcpath}/build
build.dir ${worksrcpath}/build
Thanks, that works like a charm. I’ll commit the ports now.
Vincent
Ryan,
sourceforge:project/math-atlas/Stable/${version}:atlas
Thanks. Fixed again in r122658.
Hope it works this time…
Cheers!
V.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
Ryan,
sourceforge:project/math-atlas/Stable/${version}:atlas
Thanks. Fixed again in r122658.
Hope it works this time…
Cheers!
V.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
Dobro yutro Mojca,
Location: another MacPorter lives nearby and we are willing to
organize the event together, in the middle of Europe. We could
choose between close to the sea and in the mountains. I would
certainly like to avoid the cities and try to organize the event
somewhere in the
Le 25 juil. 2014 à 10:55, Mojca Miklavec mo...@macports.org a écrit :
In 2008 we had a ConTeXt meeting in Bohinj for example.
(http://meeting.contextgarden.net/2008/, here:
http://www.csod.si/dom/bohinj?language=en). That's not the only option
though (and maybe not even the best one). Lodging
Until now up to 6 people replied that they *might* be able to show up
in Europe. If the number stays that small, we could still meet, but it
would be easier to just pick a location and go there without any big
one-year-in-advance reservations of the place.
Hi !
If it’s scheduled enough in
Please join us in welcoming the following new MacPorts committers:
- Peter Danecek (petr)
- Craig Treleaven (ctreleaven)
- Juan R. Garcia Blanco (juanrgar)
Welcome to the jungle! ;)
V.
___
macports-dev mailing list
Hi there,
would it be possible to add to the Orfeotoolbox Portfile a few lines to
display, at the end of the install phase, a message explaining how to configure
QGis 2.2 to use the library?
Thanks,
Vincent
___
macports-dev mailing list
Ryan,
the new design is rad! But I wonder if it is appropriate to use floppy disk
icons to symbolize packages. I’m pretty sure the youngest over here do not even
know what it is about ;)
(Granted, that’s just nitpicking…)
Thanks for the wonderful work.
Vincent
Folks,
I have kinda spruced up the Atlas port by moving from clang33 to clang34,
replacing an old gcc46 variant by a new gcc49, and changing the default
behavior (+clang instead of +clang33)
Now, my predicament is this: should I upgrade the revision, and force a general
rebuild in all users
Hi Marko,
great idea. I’ll attach the new Portfile right away in one of those tickets, so
that you can test it. If it works fine, then I’ll close the bug and commit it
(but still, my question remains).
Vincent
___
macports-dev mailing list
Hi Michael,
Hi Vincent - With so many fixes / changes, once the updated Portfile is
verified / fixed, my vote is to do the rev-bump. Makes future tickets
easier to work with, among other things. - MLD
Noted.
By the way, I figured out it is not very wise to change the default compiler
from
Ryan:
Well the developers seem to call it “3.0.1-alpha-0” so that’s what I would
put in the version field
Yes, but once the final 3.0.1 will be released, nobody will be able to upgrade,
since 3.0.1-alpha-0 seems to be considered by Macports as newer than plain
3.0.1 (cf. my other message on
The epoch line is no more a wart than any other line of the Portfile… it’s
just a syntax for accomplishing a task.
[…]
Thanks Blair Ryan for the explanation. I just wish there would be some other
mechanism somehow able to tweak the ‘update detection’ script. E.g, considering
that any X.Y.Z
Le 1 déc. 2013 à 10:44, Ryan Schmidt ryandes...@macports.org a écrit :
That’s not always the case. For example, libtcd was updated from 2.2.5 to
2.2.5-r3 in r114005. 2.2.5-r3 is not a development or alpha or beta or
release candidate version; it’s the third actual release of the stable
Le 2 déc. 2013 à 04:22, Ryan Schmidt ryandes...@macports.org a écrit :
We should not confuse users and developers. We should call things what they
are.
I concur with you. We’re computer scientists, not politicians :)
Vincent
___
macports-dev
Hi Ryan,
The epoch may never be removed or decreased; please put it back.
Done in r114183.
Does that mean that we can’t never get rid of that epoch wart?
Cheers!
Vincent
___
macports-dev mailing list
macports-dev@lists.macosforge.org
Blair:
That’s right, they can never be removed.
Thanks.
By the way, what was the ‘epoch’ meant for, initially?
Vincent
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Le 1 déc. 2013 à 03:53, Ryan Schmidt ryandes...@macports.org a écrit :
The port should not claim to be version “3.0.1” when it is actually an alpha
version thereof. Put the real version number in the version field.
You’re right, that was not very clever. I thought it could be managed through
Ryan,
It’s nice to commit whitespace changes separately from functional ones so
that the functional changes can be more easily spotted. This appears to be
the functional change in this commit:
I agree and apologize. The functional change was so minor I thought unnecessary
and cumbersome to
Sorry Ryan, I didn’t see your patch. I added the line very quickly as a kludge,
being somewhat swamped at work. I’ll implement your patch on the double:
r112566.
Thanks as usual!
Vincent
___
macports-dev mailing list
Le 10 oct. 2013 à 03:17, Joshua Root j...@macports.org a écrit :
This appears to be incorrect in two ways.
1. The license should be GPL-3+ (only a few files are LGPL-3+ and none
are LGPL-2)
The website states: “ SFCGAL is distributed under the terms of the GNU Lesser
General Public License
Josh,
Probably not just go ahead and call it LGPL-2 (which makes us distribute
it). You could ask the developers for clarification.
I’ll do that right away.
Most of the files are now LGPLv2 or later in the new version you just
committed. However the viewer still says GPL-3+, as do the
Le 10 oct. 2013 à 12:20, Joshua Root j...@macports.org a écrit :
Well you should just remove the unnecessary (and now old) version line.
The name line can be moved to after the github.setup to override it.
Done in r112041.
Thanks a lot!
Vincent
PS : I got a reply from the author concerning
Ryan,
Revision: 112006
[…]
Thanks for you ongoing alertness. I’ve taken into account all but one of your
remarks: I couldn’t tweak the github port to fit that obviously non-standand
repository, so I just left the master_site and all other variables as is.
Thanks once more.
Vincent
Le 1 oct. 2013 à 12:41, Ryan Schmidt ryandes...@macports.org a écrit :
Version numbers are strings, not floating-point numbers. You need to use the
[vercmp] procedure to compare them.
Thanks Ryan. Committed in r111786.
Vincent
___
macports-dev
Michael,
I have a working relationship with the lead developer of SIP. Please
send me your info off-list, whether a patch or just suggestion, along
with the error you're experiencing and how to recreate it, and I'll
forward that info to him. In the past, he has been very responsive to
Folks,
The newest version of QGis does not compile because of bug in SIP 4.15.x.
Specifically, the file qsyntaxhighlighter.sip located in
${prefix}/share/pyXX-sip/PyQt4/QtGui is buggy, and causes an error. I own a
fixed copy which allow a correct build.
Question: can I patch the
I updated py*-sip in r110025
https://trac.macports.org/changeset/110025 , which apparently provides
SIP API v10.0 to v10.1. Just now I rev-bumped py-qscintilla (me),
py-pyqt4 (me), py-pyqwt (me), and orocos-kdl (nomaintainer), just in
case even though they work for me. I see that Poppler
Hi!
I'm concerned that the net performance gain here is going to be far
outweighed by the maintenance costs and user complexity. Without actually
measuring the gains, there's no guarantee that these changes will actually
improve performance, and in moving away from the optimization flags
Le 28 juil. 2013 à 08:19, Ryan Schmidt ryandes...@macports.org a écrit :
Are you sure it's a library dependency? Usually pkgconfig is only a build
dependency. Unless one of the programs installed by spatialite (a config
program, perhaps?) internally uses pkgconfig.
You’re right Ryan.
Folks,
as part of the perf variant proposal, I have written a perf-1.0 portgroup file
that might do the job. Opinion?
Thanks,
Vincent
—
# $Id: perf-1.0.tcl vi...@macports.org $
#
# Copyright (c) 2013 The MacPorts Project
# All rights reserved.
#
# Redistribution and use in source and binary
Josh,
Air nm /opt/local/lib/libwx_osx_cocoau_html-2.9.dylib | c++filt | grep
SetHTMLWindowTitle
0004284a T wxHtmlWindow::SetHTMLWindowTitle(wxString const)
00063250 T wxHtmlListBox::SetHTMLWindowTitle(wxString const)
0004285c T non-virtual thunk to
Ryan,
+pre-configure {
+system -W ${worksrcpath} autoreconf -i
This could be done with:
use_autoreconf yes
autoreconf.args -i
So be it. But how can I then patch the generated configure file before it is
run?
Vincent
___
macports-dev
Le 27 juil. 2013 à 11:24, Clemens Lang neverpa...@gmail.com a écrit :
Why do you have to? If you're running autoreconf anyway, why not just patch
configure.in?
Of course! Thanks! Sometimes I feel I’m just stupid! ;)
Vincent
___
macports-dev
Hi there,
When I build wxWidgets30, I get these, e.g. in libwx_osx_cocoau_html:
Air nm /opt/local/lib/libwx_osx_cocoau_html-2.9.dylib | c++filt | grep
SetHTMLWindowTitle
0004284a T wxHtmlWindow::SetHTMLWindowTitle(wxString const)
00063250 T
Does doing so in a pre-configure block, exactly as you're doing now, not
work? Does that end up running before the autoreconf?
Ryan: yes. The autoreconf-configure pair seems to be atomic. Either it is run
too early, or too late.
Clemens, this is the AM_PYTHON_DEVEL ([]) if I remember
Folks,
I am going to add a new port in the ‘gis’ category. However, at this point in
time, the source code is not available for download through a direct link. I
was therefore wondering if it were possible to upload it to
packages.macports.org so that the Portfile could download it directly
Le 26 juil. 2013 à 10:17, Ryan Schmidt ryandes...@macports.org a écrit :
distfiles.m.o is for source code archives. You cannot manually upload
anything there, but you can ask the macosforge admin to do so. However there
should be no need to, assuming you can put the distfiles anywhere else
Le 26 juil. 2013 à 15:52, Daniel J. Luke dl...@geeklair.net a écrit :
well, we used to have people put files in part of our svn repo for things
that didn't have a good master site (and the mirror could just be a mirror).
At some point, we decided that this was bad, and told people to stop
Le 22 juil. 2013 à 14:52, Ryan Schmidt ryandes...@macports.org a écrit :
Possibly you should set configure.optflags -O3 -march=native instead of
dealing with cflags and cxxflags directly.
I found that setting configure.cflags and cxxflags does not seem to interfere
with the other options.
Hi Ryan,
Presumably the removal of the revision line was unintended? The revision
cannot decrease unless the version or epoch increases.
Oops, that was a mistake. I made some attempts to bump to an unstable version
that supports Haswell, but it produced buggy code, so I reverted to the
Dear base gurus ;),
is there a way to clean up the files stored in distfiles, especially those
corresponding to old port versions, but that still linger in the filesystem and
take unnecessary space?
Why ‘port clean outdated’ does not take care of this?
Just curious,
Vincent
Can you check to see if the version of the files left behind match the
oudated ones, that only the current version is being cleaned regardless of
which ones are outdated?
Do you mean it is impossible to figure out which version is tied to which
distfile? Isn’t that something that could be
Ryan,
The default for configure.optflags is -Os in MacPorts 2.2 and was -O2
previously.
The default for configure.cflags, configure.cxxflags, configure.objcflags,
configure.objcxxflags, configure.fflags, configure.f90flags, and
configure.fcflags is ${configure.optflags}.
Ok, great then.
It might have the information available (I think we stored install-time
Portfiles into the database) but I'm not sure if that's what we use when
cleaning distfiles. A quick glance in your directory should confirm this, or
a base dev looking into the source for it.
For example, I just
Le 22 juil. 2013 à 21:36, Jeremy Lavergne jer...@lavergne.gotdns.org a écrit :
Ah, so you've already uninstalled boost 1.53, hence there is no outdated
boost installed and the tracking for the file is definitely gone.
Right. My question precisely was: why does ‘port uninstall’ not wipe out
This might be semantic points at the end of the day, but…
And here in Paris the day is really close to its end! :)
You installed binaries, not source code, so only the installed files are
uninstalled. That is, source code is only used for building. If you needed
the source code before, you
Le 22 juil. 2013 à 21:41, Ryan Schmidt ryandes...@macports.org a écrit :
Hmm. I think we probably want all ports to respond correctly to
configure.compiler, since the default differs by Xcode version, but of course
we haven't audited all ports for compliance, and I'm sure several don't. But
1 - 100 of 308 matches
Mail list logo