Generally, use MacPorts for a newer python/pip and use that pip to
install subsequent modules.
There are a few cases where you may benefit from MacPorts' pre-compiled
c modules, however you won't be able to version-pin dependencies
(MacPorts doesn't appear to have this concept).
On 12/6/22
If anyone else pushed between your fetch and push, you'll be out of date
again.
Not entirely sure what your workflow is, but you a current git should
let you do an autostash on pull (which might help your situation):
git pull --rebase --autostash && git push
On 1/9/20 4:34 PM, Gerben Wierd
You can enable trace mode initially so you don't need to create a bunch
of echo statements about what you're doing:
set -xtrace
There are some other flags I'd recommend, and all of them in short form:
set -eux
On 03/04/2017 09:57 AM, Comer Duncan wrote:
> I forgot to attach my script. Not that
To that end, also check out using pip-tools along with virtualenv. This
will allow you to determine the whole set of dependencies and their
versions.
Example shell script using pip-tools inside a virtualenv for producing a
requirements.txt for `pip install --upgrade -r requirements.txt`:
#!/usr/b
The difference in paths indicates the logs you see are from the default
prefix, but you have since configured MacPorts to use a different prefix.
/opt/local versus /opt/mports
On 03/30/2017 12:26 PM, Jan Stary wrote:
> hans@macbook:~$ find /opt/local/var/macports/logs
> /opt/local/var/macports/l
There are a few options laid out:
https://guide.macports.org/#reference.livecheck
One is `livecheck.regex` to set the pattern to consider for eventual
comparison. If you keep it to solely numbers you can ignore the rc
matches: `[0-9]+(\.[0-9]+)+`
On 08/08/2017 11:16 AM, Jan Stary wrote:
> $ port
There should be a "dependents" command, showing what's installed that
needed a given package.
Something like `port dependents gcc7`
On 10/07/2017 09:01 AM, db wrote:
> I updated my ports and realised that gcc7 was built, but couldn't establish
> for which port it was necessary. I thought someth
Checkout unoconv.
https://github.com/dagwieers/unoconv
On 12/11/2017 01:59 PM, Arno Hautala wrote:
> On Mon, Dec 11, 2017 at 12:54 PM, William H. Magill wrote:
>> The .doc and text files require another step — namely saving (printing) them
>> as a PDF file first.
> I've seen a few tips on using
A (human) workaround is to verify you've typed it correctly with the
`port variants` command:
port variants bitcoin +qt5
On 01/03/2018 02:34 PM, Jan Stary wrote:
> I just built "bitcoin +qt5", only to realize its "bitcoin +gui".
> While build the noneexistent +qt5 variant, the default variant
>
On 02/12/2018 09:14 AM, db wrote:
> Would it suffice to rename /usr/local during build time to avoid any
> conflicts? I ask because I just want to make sure that I'm not missing
> anything else.
MacPorts can deny any access to Homebrew during builds in trace mode.
Less invasive than renaming fi
10 matches
Mail list logo
