Re: Dev guide updated for github/easy instructions?
I believe you’re looking for this:4.6. Local Portfile Repositoriesguide.macports.orgOn Dec 19, 2022, at 07:05, Watson Ladd wrote:On Mon, Dec 12, 2022, 1:55 PM Nils Breunesewrote:Does https://guide.macports.org/chunked/project.github.html help?A bit. What I don't know how to do is get macports to use the modified port file. The best I can figure out is use the whole different tree, which is mildly annoying if I forget to set it back. Nils. P.S. I believe macports-...@lists.macosforge.org is the old address of this mailing list, macports-dev@lists.macports.org is the new one. > Op 12 dec. 2022, om 16:35 heeft Watson Ladd het volgende geschreven: > > This morning I realized that Pari is lagging behind, so went ahead to > start contributing a version bump. Unfortunately i completely forgot > the song and dance to make Macports process the portfile I produced, > and then the documentation was very pre-github migration (assumes > individual port files vs checking out the repo). > > Perhaps we should have a development guide update, and in the meantime > do i just update the sources to include my local checkout? I could > have sworn I've done this before, but just forgot how. > > Sincerely, > Watson > > -- > Astra mortemque praestare gradatim
Re: Dev guide updated for github/easy instructions?
On Mon, Dec 12, 2022, 1:55 PM Nils Breunese wrote: > Does https://guide.macports.org/chunked/project.github.html help? > A bit. What I don't know how to do is get macports to use the modified port file. The best I can figure out is use the whole different tree, which is mildly annoying if I forget to set it back. > > Nils. > > P.S. I believe macports-...@lists.macosforge.org is the old address of > this mailing list, macports-dev@lists.macports.org is the new one. > > > Op 12 dec. 2022, om 16:35 heeft Watson Ladd het > volgende geschreven: > > > > This morning I realized that Pari is lagging behind, so went ahead to > > start contributing a version bump. Unfortunately i completely forgot > > the song and dance to make Macports process the portfile I produced, > > and then the documentation was very pre-github migration (assumes > > individual port files vs checking out the repo). > > > > Perhaps we should have a development guide update, and in the meantime > > do i just update the sources to include my local checkout? I could > > have sworn I've done this before, but just forgot how. > > > > Sincerely, > > Watson > > > > -- > > Astra mortemque praestare gradatim > >
Re: Dev guide updated for github/easy instructions?
When I used that page, step 1e was confusing to a git newbie. -- Steve From: macports-dev on behalf of Nils Breunese Date: Monday, December 12, 2022 at 4:56 PM To: MacPorts Development Subject: Re: Dev guide updated for github/easy instructions? Does https://guide.macports.org/chunked/project.github.html help? Nils. P.S. I believe macports-...@lists.macosforge.org is the old address of this mailing list, macports-dev@lists.macports.org is the new one. > Op 12 dec. 2022, om 16:35 heeft Watson Ladd het > volgende geschreven: > > This morning I realized that Pari is lagging behind, so went ahead to > start contributing a version bump. Unfortunately i completely forgot > the song and dance to make Macports process the portfile I produced, > and then the documentation was very pre-github migration (assumes > individual port files vs checking out the repo). > > Perhaps we should have a development guide update, and in the meantime > do i just update the sources to include my local checkout? I could > have sworn I've done this before, but just forgot how. > > Sincerely, > Watson > > -- > Astra mortemque praestare gradatim
Re: Dev guide updated for github/easy instructions?
Does https://guide.macports.org/chunked/project.github.html help? Nils. P.S. I believe macports-...@lists.macosforge.org is the old address of this mailing list, macports-dev@lists.macports.org is the new one. > Op 12 dec. 2022, om 16:35 heeft Watson Ladd het > volgende geschreven: > > This morning I realized that Pari is lagging behind, so went ahead to > start contributing a version bump. Unfortunately i completely forgot > the song and dance to make Macports process the portfile I produced, > and then the documentation was very pre-github migration (assumes > individual port files vs checking out the repo). > > Perhaps we should have a development guide update, and in the meantime > do i just update the sources to include my local checkout? I could > have sworn I've done this before, but just forgot how. > > Sincerely, > Watson > > -- > Astra mortemque praestare gradatim
Dev guide updated for github/easy instructions?
This morning I realized that Pari is lagging behind, so went ahead to start contributing a version bump. Unfortunately i completely forgot the song and dance to make Macports process the portfile I produced, and then the documentation was very pre-github migration (assumes individual port files vs checking out the repo). Perhaps we should have a development guide update, and in the meantime do i just update the sources to include my local checkout? I could have sworn I've done this before, but just forgot how. Sincerely, Watson -- Astra mortemque praestare gradatim