On Thu, Nov 19, 2015 at 9:49 PM, Ryan Schmidt
wrote:
> 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.
Congratulations! If that's appropriate (the Augean stables come to mind..
On Thu, Nov 26, 2015 at 10:03 AM, Mark Brethen
wrote:
> says "symbol(s) not found for architecture x86_64" instead of "symbol(s)
> not found for architecture i386”. Can I tweak my build settings to allow a
> 32-bit build?
"build_arch i386" in /opt/local/etc/macports/macports.conf to force all
b
On Thu, Nov 26, 2015 at 10:16 AM, Mark Brethen
wrote:
> I suspect the source does not support 64-bit builds. How do I tweak the
> port to build universal? Is there an example port I could look at?
Most ports will "just work", because there's a default +universal variant.
Otherwise look for port
On Thu, Nov 26, 2015 at 10:24 AM, Brandon Allbery
wrote:
> On Thu, Nov 26, 2015 at 10:16 AM, Mark Brethen
> wrote:
>
>> I suspect the source does not support 64-bit builds. How do I tweak the
>> port to build universal? Is there an example port I could look at?
>
>
&
On Thu, Nov 26, 2015 at 10:40 AM, Mark Brethen
wrote:
> The link error occurs here:
>
> :info:build /usr/bin/clang++ -c -o astgen.o astgen.cc -g -Wall
> -Wno-deprecated -D__UNIX__ -O2 -DNDEBUG -I../smbase
> :info:build /usr/bin/clang++ -o astgen gramlex.o agrampar.tab.o ccsstr.o
> agramlex.yy.o r
On Fri, Nov 27, 2015 at 1:41 PM, Vincent Habchi wrote:
> 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 bark “platforms
> do not match” each time I try to punch a command.
Reinstall from the installer for that
On Fri, Dec 4, 2015 at 10:15 PM, Mark Brethen
wrote:
> OCAMLDIR needs to be set, but what about the rest?
The only way to answer that is to see what the Makefile ends up running and
what envars those programs require.
--
brandon s allbery kf8nh sine nomine associ
On Wed, Dec 16, 2015 at 12:23 PM, Adam Dershowitz
wrote:
> Sorry I wasn’t clear. I just meant that I perl5 shows this:
> perl5 @5.22.1_0+perl5_16 (active)
>
> So, it is version 5.22 But, it ddid install 5_16.
>
That's confusing but expected; the version is the latest version it knows
about (II
On Wed, Dec 16, 2015 at 3:50 PM, Ryan Schmidt
wrote:
>
> However, that doesn't explain why, for me, the same is not happening in
> the post-destroot phase.
Seems like it might be for some people though? That would explain why some
people are reporting that a -5.22 suffixed name is being used by
On Wed, Dec 16, 2015 at 4:03 PM, Adam Dershowitz wrote:
> Does the restore_ports.tcl script handle things any differently then just
> a standard install or upgrade? For example, does it handle the order of
> installs differently?
It remembers active variants, so if you had perl5 +perl5_16 inst
On Sun, Dec 27, 2015 at 5:10 PM, René J.V. wrote:
> I renamed kf5/kate to kf5/kate5 to avoid having 2 port directories with
> identical names. That defeats the purpose of organising the port repository
> using the filesystem, but that's another topic.
The usual use case is you are making a loca
On Tue, Jan 5, 2016 at 2:24 PM, Ryan Schmidt
wrote:
> As far as I know, MacPorts does not contain anything called "perl_select".
There is, actually, but it's a stub that doesn't do anything as yet (or
probably ever since it was subsequently decided to just move to a single
Perl release).
--
b
On Wed, Jan 13, 2016 at 2:19 AM, Ryan Schmidt
wrote:
> But is that because -I/opt/local/include then gets inserted into the
> correct place in the compile line, or because -I/opt/local/include is
> omitted from the compile line and it only works because MacPorts also
> happens to set CPATH=/opt/l
On Sun, Jan 24, 2016 at 6:20 AM, René J.V. wrote:
> A trip to single-user mode or into recovery mode to toggle an EFI setting,
> right?
csrutil {enable|disable} and reboot.
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com
On Sat, Jan 30, 2016 at 5:16 AM, René J.V. wrote:
> - is there a way to silence output from `catch {system ...` even with the
> -v option? I thought the role of the catch function was also to ... catch
> the called function's output?
Tcl throws an exception if the command run via system exits n
On Sun, Jan 31, 2016 at 10:54 AM, René J.V. wrote:
> that usually led to (bogus) errors being printed about those sourced
> files, when uninstalling or de/activating ports
The Portfile is stored in the registry (otherwise, what happens when
there's a script that needs to be run on uninstall or
On Sun, Jan 31, 2016 at 11:09 AM, René J.V. wrote:
> The same argument can apply to PortGroups ... or are those stored in the
> registry?
They're in the ports tree, but they don't get removed. If you look in the
port resource directory you'll see where old versions of PortGroups are
retained ev
On Mon, Feb 1, 2016 at 2:11 PM, René J.V. wrote:
> - letting `port checksum` update the checksums removes much of the
> interest of verifying checksums ("the checksum doesn't match, do you want
> to update it?")
I would expect that you would need an option to enable updating, and get
the curren
On Sun, Feb 7, 2016 at 3:00 PM, David Evans wrote:
> Same here. New form of spam?
gmail calendar support gone wonky, look like. I get that calendar link from
the original message, but the quoted one in Bradley's message is correct.
--
brandon s allbery kf8nh sin
On Mon, Feb 15, 2016 at 9:33 PM, Mihai Moldovan wrote:
> > An example would be a "check and try update" task that would: do a
> > livecheck and if found to be old then automatically try to do the
> > update: change the version, download the distfile, update the checksums
> > in the Portfile, try
On Mon, Feb 15, 2016 at 11:43 PM, Bradley Giesbrecht
wrote:
> I have a bunch of scripts for creating patches, checking for updates,
> checking trac for tickets, svn {st,diff,ci} etc…, and I know others do to.
> I don’t know if TCL has this capability but I would be handy at times to
> dump all de
On Wed, Feb 24, 2016 at 10:12 AM, Chris Jones
wrote:
> Been ages since I ran 10.6, so I might have forgotten where things are in
> that OS, but have you checked the OSX App Store for Xcode ?
Xcode before 4.0 was not available via the App Store, as it installed under
/Developer instead of as a s
On Tue, Mar 1, 2016 at 10:35 AM, Mojca Miklavec wrote:
> The question is: should I bother upstream (wxWidgets) with trying to
> circumvent the problem? It probably makes no sense to report the
> compiler problem to anyone (clang/apple developers) as it is most
> likely fixed already (clang-3.4 wo
On Thu, Mar 10, 2016 at 1:48 AM, Mojca Miklavec wrote:
>
> When I was testing wxWidgets, discovered a problem and submitted a
> patch, I noticed what they are doing now (which is some light years
> more advanced compared to what they did a few years back when most of
> the tickets were stuck igno
On Thu, Mar 10, 2016 at 8:20 PM, Mojca Miklavec wrote:
> >> on 10.6/x86_64 I tried to install clang 3.7 (thinking that version 3.7
> >> might have an even better support for PPC than 3.6).
I just noticed this... my own assumption would be that, as availability of
PPC test hosts is ever-decreasi
On Sat, Mar 26, 2016 at 7:36 PM, André-John Mas
wrote:
> I am trying to update the mediainfo port to 0.7.83, though there are
> changes beyond the
> version number that need to be made.
>
> Based on suggestion of the application developer I am trying to base the
> updated Portfile
> on that recip
On Wed, Mar 30, 2016 at 9:45 PM, Mark Brethen
wrote:
> According to the documentation these parameters are actually the names of
> shell scripts that CGX runs to open the viewers. For example, the
> instruction for the html viewer are as follows:
This is because Linux's story for handling this
On Thu, Mar 31, 2016 at 11:56 AM, Rainer Müller wrote:
> A better way could be to handle SIGINT/SIGQUIT in a custom handler and
> on reception of a signal, we would kill the child process and return the
> error {POSIX SIG SIGINT} as result of SystemCmd. However, I am unsure
> how we would force t
On Fri, Apr 1, 2016 at 5:16 PM, Fred Wright wrote:
> Actually, that specific problem is fixed by the switch to 'python2' in the
> shebang lines in 3.16, but then you need to have a 'python2'.
>
As you were told, the correct fix is to depend on a specific Python version
*and use that*. Your propo
On Mon, Apr 11, 2016 at 5:19 PM, David Strubbe
wrote:
> Of course it's not a full solution, but this seems like a fairly simple
> advance that will solve some problems.
Last year had a GSoC project to add a SAT-solver based dependency engine;
it has, among other things, variant support. I belie
On Thu, Apr 14, 2016 at 11:24 PM, Abdulrahman Alshammari <
a.tu...@hotmail.com> wrote:
> I was asked to change some parts of portfile. I did that except the
> checksums. I was told that the checksums will be changed because the github
> port. Can someone let me know how I can change it since using
Ziad Ali" instaed of "Abdulrahman
> Alshammari".
> This is an issue that I am trying to fix.
>
> On Apr 15, 2016, at 8:39 PM, Brandon Allbery wrote:
>
> On Thu, Apr 14, 2016 at 11:24 PM, Abdulrahman Alshammari <
> a.tu...@hotmail.com> wrote:
>
>>
On Mon, Apr 18, 2016 at 4:12 PM, Mojca Miklavec wrote:
> Apparently USA export
> restrictions forbid exporting software that does cryptography
Umm, ITAR's had an OSS exemption for years. Are you reading old information?
> (and
> some other countries might have import restrictions).
>
Sadly s
On Sat, Apr 23, 2016 at 9:18 PM, Abdulrahman Alshammari wrote:
> Error: Unable to execute port: Could not open file:
> /Users/Abdulrahman/Desktop/ports/devel/civl/Portfile
>
By default the "macports" user that is used to do builds etc. MacPorts
tries to avoid actually doing things as root unless
On Sat, Apr 23, 2016 at 9:40 PM, Abdulrahman Alshammari wrote:
> I added the permission of macports users from get info of the file but it
> has the same issue. Do you mean we change the ACLs for only the portfile?
> or the whole directory?
>
"Remember that it needs at least "search" ("execute"
On Wed, Apr 27, 2016 at 10:49 AM, Abdulrahman Alshammari <
a.tu...@hotmail.com> wrote:
> build {
>system -C ${worksrcpath} "java -jar filename.jar”
> }
>
>
> After changing the file name and others, It gives me that
> Error: org.macports.build for port civl returned: bad option -C
>
I think i
On Tue, May 3, 2016 at 8:10 PM, Abdulrahman Alshammari
wrote:
> The attached portfile is working now perfectrly after fixing some issue. I
> am not sure if what I did is the right one or there is something better
> than this. When I install civl, it works fine, but when I uninstall it, the
> file
On Fri, May 13, 2016 at 4:07 AM, René J.V. wrote:
> I'm curious though, what ports rely on i386 meaning "Intel, 32 or 64 bit"
> rather than "Intel, 32 bit", directly in their Portfile rather than
> indirectly through "base"? I find that confusing and it often makes me
> pause when I see the term
On Fri, May 13, 2016 at 10:40 AM, Vincent Habchi wrote:
> Yep, but I commented the line below, and it compiled fine. So this comment
> must somehow be outdated.
I'd only trust that if you built it in trace mode.
--
brandon s allbery kf8nh sine nomine associates
a
t 10:46 AM, René J.V. wrote:
> On Friday May 13 2016 10:11:50 Brandon Allbery wrote:
>
> > Remember that OS X goes to great lengths to hide 32 vs. 64 bit
> > distinctions; 32 bit OS X kernels were perfectly capable of running 64
> bit
> > binaries on 64-bit CPUs, a
On Wed, May 18, 2016 at 5:46 PM, René J.V. wrote:
> This got me thinking about more elegant ways to avoid the issue, in
> particular Debian/Ubuntu's approach of distinguishing "user" packages and
> "developer" packages. The former contain everything required to use the
> package, other than for d
On Sat, May 21, 2016 at 10:33 AM, René J.V. wrote:
> May 21 16:20:08 Portia kernel[0]: CODE SIGNING:
> cs_invalid_page(0x105ead000): p=98132[kioslave] final status 0x0, allowing
> (remove VALID) page
So what I'm seeing is that this indicates that something is corrupted and
making the kernel thi
paid less
attention to newer OSes)
On Sat, May 21, 2016 at 12:51 PM, René J.V. wrote:
> On Saturday May 21 2016 11:02:58 Brandon Allbery wrote:
>
> > invalid. This can be as simple as /private/etc/authorization being
> corrupt
>
> Should I have that file (on 10.9)? I only have
&
On Sat, May 21, 2016 at 8:01 PM, Bradley Giesbrecht
wrote:
> OpenSSL might be able to accomplish the same task and it is possible with
> OpenSSL to write a config file that fills in all the required fields. Port
> could write such a config per user.
OpenSSL can certainly create the signing cert
On Tue, May 31, 2016 at 4:24 AM, René J.V. wrote:
> That's a pity. I had quite a few if {${os.platform} eq "darwin"} {} else
> {} statements in certain of my ports, which I most all replaced with
> platform statements at the suggestion to do so.
Is there some reason you can't invert the logic?
On Tue, May 31, 2016 at 9:24 AM, Marcus Calhoun-Lopez wrote:
> /usr/bin/defaults exists and is working.
> The foreach loop seems to be looping over the correct values.
> For some reason, however, /usr/bin/defaults seems to be either
> (1) failing to create Info.plist (but doing so without gen
On Fri, Jun 3, 2016 at 5:41 AM, René J. V. wrote:
> It turns out that access to the user's default keychain is wonky during the
> post-activate stage
>
Ideally it shouldn't be allowing access to the user's chain at all.
post-activate is a system level operation, not user level.
--
brandon s al
On Sat, Jun 11, 2016 at 11:51 AM, JASON TILLEY wrote:
> I am attempting to create my first port in a local repository. I can get
> it to configure, but it seems to be having trouble installing into
> destroot. I get the error:
>
> for i in libnn.a; do \
>/usr/bin/install -c -m 644 $i /opt/loc
On Fri, Jun 17, 2016 at 12:38 PM, Alexey Kuznetsov <
kuznetsov.ale...@gmail.com> wrote:
> I think this is step in the right direction make all packages support for
> the same format. Having same portfile format (.yaml format) for all distros
> is very nice.
You're missing the point that those di
On Fri, Jun 17, 2016 at 1:34 PM, Alexey Kuznetsov <
kuznetsov.ale...@gmail.com> wrote:
> I think snapd is a good point to try to start to be together. May be
> because no one tried three separate build system exists on Mac. Why waste
> people energy by supporting all of them instead of good collab
On Sat, Jun 18, 2016 at 12:35 AM, Alexey Kuznetsov <
kuznetsov.ale...@gmail.com> wrote:
> I read emerying carefully. Very informative. But you missing a point. I'm
> not talking why it is not possible. Do you think all Linux distoros more
> compatible between each other than Mac with three build
>
On Sat, Jun 18, 2016 at 12:54 AM, Brandon Allbery
wrote:
> system's? They all have problem you mention, including absolute path
>> linking (they are using same liking tools) and more! But they all
>> understand they need to be together and they find the way. I'm
On Thu, Jul 14, 2016 at 11:07 AM, Daniel J. Luke wrote:
> I don't think it's useful to define a status for "it's unclear which
> version of a license this falls under". (what kind of decisions would we
> make based on that data?)
"this license is underspecified; prod someone to fix it"
--
br
On Sun, Jul 17, 2016 at 2:16 AM, Joshua Root wrote:
> The second question is about names: I named the port chez-scheme.
>> Unfortunately the tarball they have expands into one with a directory
>> named ChezScheme-9.4 and not chez-scheme-9.4 The obvious thing to do
>> is to change the name of the
On Tue, Jul 19, 2016 at 11:14 AM, David Evans wrote:
> On 7/19/16 8:04 AM, Ryan Schmidt wrote:
> >> Thanks, Ryan. Fixed in r150468. I'm surprised that there aren't more
> of these since the 'version' module which aims to
> >> normalize perl version numbers always includes the 'v' prefix in the
On Wed, Jul 20, 2016 at 7:21 PM, Sean Farley wrote:
> OpenMPI just released 2.0 which will change the name of the libraries.
> I'm guessing I should revbump all the dependents to force a rebuild but
> is this something that `port rev-upgrade` should handle?
>
I think you can get into trouble wit
On Thu, Aug 11, 2016 at 2:20 AM, Lawrence Velázquez
wrote:
> Which is unexpected to say the least. It's because "os" gets hijacked as a
> variable name, around line 440:
And I have another reason to dislike Python. *Why* are those in the
same namespace?! You basically cannot trust code that
On Thu, Aug 11, 2016 at 12:09 PM, Russell Jones <
russell.jo...@physics.ox.ac.uk> wrote:
> Python has a concept of "we're all consenting adults here"
Who deposed Guido? Python's usual concept is "This Is The One True Way and
we reserve the right to mock you for writing Perl in Python and then ma
On Fri, Aug 19, 2016 at 11:16 PM, Ian Wadham wrote:
> Qt and KDE moved from svn to git a while back. IIRC it was quite an
> effort for a
> few individuals to port all the repositories across and preserve all the
> history.
> They had to write lots of scripts and check all the results. I hope it
On Sat, Aug 20, 2016 at 11:44 PM, Ian Wadham wrote:
> Fork the repo??
github expects you to do this, yes. I don't actually recommend it because
keeping up to date with the original repo's a PITA (and *not* automated in
any way. https://help.github.com/articles/syncing-a-fork/ is annoyingly
manu
On Wed, Aug 31, 2016 at 4:57 PM, René J.V. Bertin
wrote:
> The real problem is going to be with the code-signing. This is done
> automagically by lldb's Xcode projects so it's not entirely clear which
> files have to be signed ... nor if an "ad-hoc" signing identify ("-") will
> lead to a usable
On Fri, Sep 2, 2016 at 1:25 PM, René J.V. Bertin
wrote:
> I guess we'll be seeing port:llvm-3.9 provide 3.9.0 in a near future, but
> what does that ABI remark mean for us on OS X? Will it again be easier to
> build C++ code using GCC? Or will it be easier for older OS X versions to
> migrate to
On Mon, Sep 5, 2016 at 8:10 PM, Fred Wright wrote:
> But when they switched to Intel, they also switched
> to -O2. This allowed them to inflate the performance benefit of the
> architecture switch. :-)
>
...as long as -O2 worked. Experience from FreeBSD and from early MacPorts
experiments with
On Mon, Sep 5, 2016 at 9:26 PM, Fred Wright wrote:
> Interesting, given that the Linux kernel *requires* optimization to build
> correctly, due to some issue with macros vs. inline functions. Of course
> that's gcc, not clang, and it doesn't necessarily rule out -Os.
>
Yes. And I was talking ab
On Tue, Sep 6, 2016 at 5:56 AM, Mojca Miklavec wrote:
> I recently figured out that ports that I have in my local repository
> are *never* updated from the binary archives, but always compiled from
> sources. MacPorts doesn't even try to fetch the binary archives, it
> goes straight to fetching t
On Sat, Sep 10, 2016 at 12:14 PM, Jeremy Huddleston Sequoia <
jerem...@apple.com> wrote:
> Please file radars and point me to them, so I can make sure they get
> routed to the right place (likely as dupes, but dupes are very useful
> "votes" for bugs).
I just noticed this. Received wisdom "out h
On Tue, Sep 13, 2016 at 12:24 AM, Jeremy Sequoia wrote:
> I just noticed this. Received wisdom "out here" is that ``nobody is
> listening and nobody ever responds, so don't bother filing radars.''
>
>
> That is very very very false.
>
That may be, but I got paraphrases of that response from a nu
On Sun, Sep 18, 2016 at 8:24 PM, Jeremy Huddleston Sequoia <
jerem...@apple.com> wrote:
> > Anyway, I don't see any valid reason why the macports user would have a
> fullblown icon cache. In my case each cache directory eats up about 900Mb.
> Some may find that insignificant; I still consider it a
On Sun, Sep 18, 2016 at 8:41 PM, Brandon Allbery
wrote:
> Some port somewhere likely builds the icon cache while building or
> "installing" (destrooting) since it "knows" that it would only be built by
> the person intending to use it and that nobody uses packaging o
On Thu, Sep 22, 2016 at 3:32 PM, Adam Dershowitz wrote:
> One other question. As openmodelica uses cmake to build. Is it likely
> that the bug in cmake is also affecting openmodelica (cache, links, stored
> paths etc)? Or, instead is it more likely that each happens to have the
> identical pro
On Mon, Sep 26, 2016 at 5:45 AM, Ryan Schmidt
wrote:
> I can't guarantee this won't mess something up, but I think you can
> already delete the /opt/local/var/macports/build directory and replace it a
> symlink to another volume
Works fine. Did that on my MacBook Air.
--
brandon s allbery kf8
On Thu, Sep 29, 2016 at 4:28 PM, Daniel J. Luke wrote:
> On Sep 29, 2016, at 3:51 PM, Lawrence Velázquez
> wrote:
> > Our blanket policy is to support the three most recent major OS
> > versions.
>
> unless policy has actually changed (and I somehow missed it), the policy
> is current release an
On Mon, Oct 3, 2016 at 10:35 PM, Alexander Gaenko wrote:
> This situation could be remedied by using Boost variant compiled with
> the "new" ABI --- however, there seems to be no such variant in the
> Boost port.
>
What OS X / macOS version? Boost should build with whatever the default C++
ABI i
On Wed, Oct 5, 2016 at 5:41 PM, Rainer Müller wrote:
> On 2016-10-05 11:09, René J.V. Bertin wrote:
> > Quick question: a normal (non-forced) upgrade currently does
> >
> > 1) install (create new tarball image)
> > 2) deactivate old
> > 3) activate new
> > 4) clean ${workpath} (unless -k)
>
> Can
On Thu, Oct 6, 2016 at 12:25 PM, René J.V. Bertin
wrote:
> Actually, that hasn't yet caused me any problems on Linux. I've made the
> v6 collection the default as soon as it became available, and certainly
> haven't had to rebuild anything because of it.
You haven't seen the work distribution f
On Thu, Oct 6, 2016 at 12:49 PM, René J.V. Bertin
wrote:
> On Thursday October 06 2016 12:32:24 Brandon Allbery wrote:
> Hasn't this become easier at all?
>
Only if you can use the GPL3 libstdc++. Since the stuff Apple ships
doesn't, we lose. Linux of course does no
On Fri, Oct 7, 2016 at 12:43 PM, Chris Jones
wrote:
> On 07/10/16 17:39, Craig Treleaven wrote:
>>
>> On Oct 7, 2016, at 12:16 PM, Sterling Smith
>>> wrote:
>>> On Oct 7, 2016, at 7:20AM, Chris Jones wrote:
My point still stands though, you have to actively try the things you
nee
On Fri, Oct 7, 2016 at 1:31 PM, Marcel Bischoff
wrote:
> 'push --force' should *never* be used when working in a team except for
> dire emergencies like having cleaned the history of accidentally
> committed login credentials or the like.
>
I only wish other projects actually did this... rewriti
On Fri, Oct 7, 2016 at 2:38 PM, Daniel J. Luke wrote:
> the cool kids also aren't writing 'tcl' these days ...
...but the way they write anything else, they might as well be writing
fortran...
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com
On Fri, Oct 7, 2016 at 5:11 PM, Davide Liessi
wrote:
> On the other hand there is nothing wrong in rewriting history in a
> temporary development branch (such as a branch for a pull request)
> before merging to a long living branch.
>
as long as it never got pushed upstream, yes. If it did, and
On Sat, Oct 8, 2016 at 4:12 PM, Marcel Bischoff
wrote:
> I for one don't understand why one would carry around all that baggage
> anyhow. Why not leave the old Trac as is and start fresh with a simple,
> reduced issue tracker
>
When the simple reduced tracker is, as already said, too simple. It
On Sat, Oct 8, 2016 at 4:27 PM, Chris Jones
wrote:
> What concerns me is the statement that in this migration to github, github
> and trac are kept completely separate, with no automatic linkage, but still
> contributors are expected to use both.
What I heard was that, due to time constraints,
On Sat, Oct 8, 2016 at 7:48 PM, Marcel Bischoff
wrote:
> I understand that. Many long-running projects are using their own Git
> infrastructure with Trac, Redmine and others. What I don't understand is
> why moving to GitHub at all when the tooling is clearly insufficient for
> the project. The a
On Fri, Oct 14, 2016 at 10:30 AM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
> how exactly do I best find that process to "fg" it again? If I just log
> back in and "fg" it, it is not found. but top shows the process is humming
> away in the background, as expected
>
You can't; it's
"port provides" actually does some extra work to normalize paths before
querying; I believe René is looking for the underlying database, and
possibly its constraints (e.g. whether it includes inactives --- which I
don't think it does).
On Fri, Oct 28, 2016 at 3:20 PM, Ken Cunningham <
ken.cunningh
On Mon, Oct 31, 2016 at 12:38 AM, Lawrence Velázquez
wrote:
> Old habits die hard, but from now on do NOT refer to Trac tickets as
> "#12345" in your commit messages; GitHub's website interprets those as
> pull request numbers. Copy and paste the full Trac URL instead.
>
Sounds like a job for a
You can even configure so that becomes the default for "git pull" for that
repo.
git config --local --bool pull.rebase true
git config --local --bool rebase.autoStash true
On Mon, Oct 31, 2016 at 7:08 PM, Eric A. Borisch
wrote:
> I hoped someone would point me to a command like this. Thanks!
>
On Mon, Oct 31, 2016 at 10:05 PM, Lawrence Velázquez
wrote:
> new 8ed388e berkeleygw: Remove svn $Id$ line.
btw, given that it's not being automated because of the unnecessary builds
it would trigger, I would say don't bother making commits that *only*
remove the Id line. It's not harmful; it's
On Tue, Nov 1, 2016 at 12:40 PM, Eric A. Borisch
wrote:
> As should the fact that, for this to work, you need to be using a
> new-enough git (like from ports) and not the system-provided one.
I would recommend that anyway, considering that the system one may be
missing things like a moderately
On Tue, Nov 1, 2016 at 1:11 PM, Clemens Lang wrote:
> I don't understand how bzip2 and port rev-upgrade relate.
I think that's a hack: save and nuke the port in question (manually), then
let rev-upgrade catch the broken dependents for you.
--
brandon s allbery kf8nh
On Wed, Nov 2, 2016 at 6:42 PM, Clemens Lang wrote:
> > When we were originally planning the transition to GitHub, I suggested
> > that we allow an "@" syntax in the maintainers line for GitHub
> > usernames (i.e. "maintainers @neverpanic" for Clemens). I don't
> > remember right now why we then
On Wed, Mar 26, 2014 at 10:37 AM, Joshua Root wrote:
> My reading of RFC 5322 is that the header field names are case-insensitive.
>
RFC5322 is one thing, the reality of spam traps another. De facto, it's
often assumed that non-normalized case is "suspicious". And good luck
getting major mail hu
On Fri, Apr 4, 2014 at 4:39 AM, Mojca Miklavec wrote:
> I wonder why libperl.dylib ends up under
> $prefix/lib/perl5/5.x.y/darwin-thread-multi-2level/CORE/libperl.dylib
> when perl5.x.y is supposed to be binary compatible with perl5.x.z.
>
That's Perl's own packaging doing (and requiring) that
On Fri, Apr 4, 2014 at 10:26 AM, Daniel J. Luke wrote:
> On Apr 4, 2014, at 10:00 AM, Brandon Allbery wrote:
> > People are still trying to figure out how to deal with perl ports; there
> was a recent aborted attempt at building a port select mechanism for it
> instead of that
On Fri, Apr 4, 2014 at 7:01 PM, Ryan Schmidt wrote:
> In this case, the dependency isn’t for more than just the perl executable,
> is it? The port does build and install perl modules, but it installs them
> in a pidgin-specific location, not in the versioned directory for whatever
> version of per
On Fri, Apr 4, 2014 at 7:46 PM, Ryan Schmidt wrote:
>
> On Apr 4, 2014, at 18:05, Brandon Allbery wrote:
> > If they're pure perl then that might work; if there's any XS involved
> then a hard version dependency would be needed.
>
> How would we determine that?
>
On Sat, Apr 5, 2014 at 1:59 AM, Mojca Miklavec wrote:
> I also agree. (But maybe keep support for Perl 6 as a separate port(?) in
> mind.)
>
Perl 6 is different enough that there's not much point in trying to fit it
into this.
--
brandon s allbery kf8nh sine nomin
On Mon, Apr 7, 2014 at 10:20 AM, Mojca Miklavec wrote:
> I see that mysql55 for example installs man pages to
> $prefix/share/man/mysql55/man1/*.1.gz
> where they are not really functional.
>
> Is that a proper place for these files? / Is there any better place?
>
If you arrange for them to
On Mon, Apr 7, 2014 at 10:40 AM, Mojca Miklavec wrote:
> On Mon, Apr 7, 2014 at 4:22 PM, Brandon Allbery wrote:
> > On Mon, Apr 7, 2014 at 10:20 AM, Mojca Miklavec wrote:
> >> I see that mysql55 for example installs man pages to
> >> $prefix/share/man/mysql55/man1
On Sun, Apr 13, 2014 at 10:39 AM, wrote:
> But if I let port show me all kmymoney4-devel deps it gets listed:
> —
> $ port rdeps kmymoney4-devel
> ...
> kde4-runtime
> kdelibs4
> soprano
> libiodbc
> gtk2
> gtk-doc
> …
> —
>
> So, the question is, why the
1 - 100 of 235 matches
Mail list logo
