Re: how to efficiently work through generating patches using git and macports build process?

On Aug 30, 2017, at 10:44, Ken Cunningham wrote: > When trying to fix broken ports, I have so far been using the method of > copying the source file to source.orig, editing the source files in place, > and then noting the files I worked on, to individually diff them at the end > to individual

Re: how to efficiently work through generating patches using git and macports build process?

All this is very helpful. Thanks! Ken > Hope this helps! - MLD > > On Wed, Aug 30, 2017, at 12:50 PM, Ken Cunningham wrote: >> >> On 2017-08-30, at 9:41 AM, Michael Dickens wrote: >> >>> What Mojca wrote is what I do too. Simple but very effective! - MLD >>> >> >> Is there a way to make

Re: Why does macports require a migration across major version bumps?

Hi, On Tue, Aug 29, 2017 at 06:01:36PM -0700, Eitan Adler wrote: > What is the underlying reason to require a reinstall across major > versions? I did something silly/stupid/smart and removed the check > from libexec/macports/lib/macports1.0/macports.tcl and just did 'sudo > port upgrade

Re: how to efficiently work through generating patches using git and macports build process?

You can always create or add them to a .gitignore file. If at the top- level GIT repo, this file impacts the whole repo. You would literally add "*.o" (but without the ""s) to this file to ignore all *.o files. Just be careful to not ignore port-original files. Example of how I do it; slightly

Re: how to efficiently work through generating patches using git and macports build process?

On 2017-08-30, at 9:41 AM, Michael Dickens wrote: > What Mojca wrote is what I do too. Simple but very effective! - MLD > Is there a way to make git ignore the *.o and *.a and other generated files that might be in the source tree that we're not interested in tracking -- or does the -A do

Re: how to efficiently work through generating patches using git and macports build process?

> >cd $(port work foo) >cd foo-version >sudo git init . >sudo git add -A > >git diff > /tmp/my-patches.diff > > And more or less make sure that you don't do "sudo port -v install" > without, say the "-k" flag to keep the files before your run "git > diff". > This is

Re: how to efficiently work through generating patches using git and macports build process?

On 30 August 2017 at 18:10, Ken Cunningham wrote: > >> Didn't we have a set of "shortcuts" that included the commands for >> setting up the local GIT repo? Might be worthwhile for folks with such >> shortcuts to push a link to this list (again). - MLD > > I do use a git repo to branch the macports

Re: how to efficiently work through generating patches using git and macports build process?

Hi Ken - I, for one, would strongly encourage you to use the GIT process you mention. You still have to be careful to distinguish between patchfiles and reinplace patches, but hopefully that's not too difficult. Another benefit to using GIT is that if you messed up a fix, you can always revert it

Re: Fixing pypi2port

> On 30 Aug 2017, at 15:12, Rainer Müller > wrote: > > On 2017-08-30 13:06, Mojca Miklavec wrote: >> Do we have any guidelines about how to properly fix ports whose >> sources lived in out subversion repository? > > The sources are now here in

Re: Fixing pypi2port

On 2017-08-30 13:06, Mojca Miklavec wrote: > Do we have any guidelines about how to properly fix ports whose > sources lived in out subversion repository? The sources are now here in macports-contrib: https://github.com/macports/macports-contrib/tree/master/pypi2port > The pypi2port sources

Fixing pypi2port

Hi, Do we have any guidelines about how to properly fix ports whose sources lived in out subversion repository? The pypi2port sources should be updated to: - switch from svn to git for the source - replace py34 with 36 - fix master_sites to use the new pypi syntax I think that perl modules also

Re: Why does macports require a migration across major version bumps?

On 30 August 2017 at 03:01, Eitan Adler wrote: > What is the underlying reason to require a reinstall across major > versions? I did something silly/stupid/smart and removed the check > from libexec/macports/lib/macports1.0/macports.tcl and just did 'sudo > port upgrade outdated' to rebuild the