I just ran `port sync`, but the ports are several days behind the GitHub
repository.
I have never encountered this before and am at a bit of a loss as to how to
proceed.
Is anyone else having this problem?
-Marcus
I think the command your after is.
$ git push origin :seqan_update ;
read it as
git push origin NULL:seqan_update
This works for tags as well as branches, assuming the name is unique.
It won't delete the local branch.
For everyone else if they do the following, it will clean up remote
referenc
Hi All,
I accidentally pushed my local branch for these changes before merging it. So
apparently there is now a branch called seqan_update that is on master. How do
I delete it?
Anyone can also please just delete it for me if you know how. The changes have
been applied to master successfully.
On Thu, 29 Dec 2016, Joshua Root wrote:
> On 2016-12-29 11:53 , Fred Wright wrote:
[...]
> > It's unfortunate that there isn't a command to give you a simple
> > category/port relative path.
>
> port info --portdir libuv
Ah, OK. I'd tried "port dir" but not that. Though for this purpose what
yo
The -N flag works for me.
sudo port -N install …
Cheers!
Frank
> On Dec 30, 2016, at 7:49 AM, Sterling Smith wrote:
>
> Hi,
>
> So it seems there is a new feature that asks if I want to install all of the
> dependencies of a requested port. Is there a command line switch to answer
> yes?
On Friday December 30 2016 17:25:20 Mojca Miklavec wrote:
> I would agree that it would be helpful to have some "more advanced"
> version of dependency specification available.
The depspec syntax doesn't necessarily have to be more complicated. Ports that
require more advanced functionality could
On Dec 30, 2016, at 09:57, Arno Hautala wrote:
>
> you
> could always work around that by using a separate GitHub account for
> your MacPorts work. That's less than ideal though.
It's also prohibited by the GitHub terms of service. Don't do that. A single
human user should have only a single Git
On 30 December 2016 at 11:32, René J.V. Bertin wrote:
> Hi,
>
> I'm coming back to this discussion because of something that came up
> elsewhere.
>
> I think we had a consensus a while back that the implementation of the
> support for using libressl at user discretion left a bit to desire.
I agr
On 30 December 2016 at 16:57, Arno Hautala wrote:
> On Fri, Dec 30, 2016 at 10:43 AM, Mojca Miklavec wrote:
>> (a) Press the button to merge the changes, but the disadvantage is
>> that committer's email is then "quasi-random" (it cannot be configured
>> on per-project basis and I would get my pers
On Fri, Dec 30, 2016 at 10:43 AM, Mojca Miklavec wrote:
> (a) Press the button to merge the changes, but the disadvantage is
> that committer's email is then "quasi-random" (it cannot be configured
> on per-project basis and I would get my personal email there instead
> of the macports one).
Unle
On 29 December 2016 at 19:30, John Patrick wrote:
> From a users point of view, it's not clear what I should be doing and
> how Ticket's link with Pull Requests and vs versa?
Neither is this entirely clear to us :) :)
But I feel that it doesn't make so much sense to have both opened at
the same t
Hi,
So it seems there is a new feature that asks if I want to install all of the
dependencies of a requested port. Is there a command line switch to answer
yes? If not, is there some other programmatic way to answer yes? (This is
installing for a non-default prefix from the master branch, so
On 2016-12-30 09:31, Mojca Miklavec wrote:
> I don't think it's possible to fetch a file nc.h and store it under a
> different name like v4.4.1.1-nc.h for example?
That could be done with the ?dummy= workaround:
https://trac.macports.org/wiki/PortfileRecipes#fetchwithgetparams
Rainer
Hi,
I'm coming back to this discussion because of something that came up elsewhere.
I think we had a consensus a while back that the implementation of the support
for using libressl at user discretion left a bit to desire.
There could be a protection against installing binary packages built agai
Hi,
I was playing with a port for comparing NetCDF
https://trac.macports.org/ticket/53118
The software depends on netcdf, but also wants to have access to two
headers that are only available in original netcdf sources and not
installed anywhere.
What's the best way to handle this?
I could:
15 matches
Mail list logo
