Re: Dealing with a port that uses github submodules

2018-05-23 Thread Ken M
On Wed, May 23, 2018 at 07:58:47AM +0100, Stuart Henderson wrote: > On 2018/05/22 23:45, Ken M wrote: > > I started fresh in my own /usr/ports/me/audio/lmms area as I was not sure > > if it > > was best to start from the existing lmms port or start anew. I went for > > anew for > > now. > > Port

Re: Dealing with a port that uses github submodules

2018-05-23 Thread Ken M
On Wed, May 23, 2018 at 07:58:47AM +0100, Stuart Henderson wrote: > On 2018/05/22 23:45, Ken M wrote: > > I started fresh in my own /usr/ports/me/audio/lmms area as I was not sure > > if it > > was best to start from the existing lmms port or start anew. I went for > > anew for > > now. > > Port

Re: Dealing with a port that uses github submodules

2018-05-23 Thread Stuart Henderson
On 2018/05/22 23:45, Ken M wrote: > I started fresh in my own /usr/ports/me/audio/lmms area as I was not sure if > it > was best to start from the existing lmms port or start anew. I went for anew > for > now. Ports infrastructure handles /usr/ports/mystuff/(category)/(port) (exactly the word "m

Re: Dealing with a port that uses github submodules

2018-05-22 Thread Ken M
On Tue, May 22, 2018 at 04:17:53PM +0100, Stuart Henderson wrote: > On 2018/05/22 09:48, Ken M wrote: > > So the port in question is lmms, since I got it to compile manually to the > > current version I figured might as well go with updating the port. > > > > They do have release tgz files hosted

Re: Dealing with a port that uses github submodules

2018-05-22 Thread Stuart Henderson
On 2018/05/22 09:48, Ken M wrote: > So the port in question is lmms, since I got it to compile manually to the > current version I figured might as well go with updating the port. > > They do have release tgz files hosted on github but those release tarballs > don't > actually include the submodu

Re: Dealing with a port that uses github submodules

2018-05-22 Thread Ken M
So the port in question is lmms, since I got it to compile manually to the current version I figured might as well go with updating the port. They do have release tgz files hosted on github but those release tarballs don't actually include the submodule that is the problem. I will contact them, co

Re: Dealing with a port that uses github submodules

2018-05-21 Thread Stuart Henderson
The best choice where possible is for upstream to generate tarballs, they can upload them to github as "release assets" for hosting, these show up in the releases page if available. -- Sent from a phone, apologies for poor formatting. On 22 May 2018 04:58:53 Thomas Frohwein wrote: On Mon, Ma

Re: Dealing with a port that uses github submodules

2018-05-21 Thread Thomas Frohwein
On Mon, May 21, 2018 at 11:32:32PM -0400, Ken M wrote: > Been trying to find a how to on this anywhere and I am not having any luck. I > found FreeBSD documentation and I found some old emails about making it a > separate port. It seems cleaner to me to have a way to recursively load so the > upstr

Dealing with a port that uses github submodules

2018-05-21 Thread Ken M
Been trying to find a how to on this anywhere and I am not having any luck. I found FreeBSD documentation and I found some old emails about making it a separate port. It seems cleaner to me to have a way to recursively load so the upstream make files work as expected.