I believe I was the one who created and maintained the spec.in files, but
for SuSE. I didn't need to change them much over the years I needed them.
Used them to create the RPM's I distributed. I didn't distribute CentOS
RPM's but they can certainly be easily adapted for that.
Curt, WE7U
http://wet
Git Pull submitted.
--David
KI6ZHD
On 07/09/2016 10:09 AM, David Ranch wrote:
Hey Tom,
If you rilly would like to get git-centric, try forking the project
on github, make a branch, make this modification on it, and submit a
pull request.
Ok.. I already had a Github account, forked Xast
Hey Tom,
If you rilly would like to get git-centric, try forking the project on
github, make a branch, make this modification on it, and submit a pull
request.
Ok.. I already had a Github account, forked Xastir, did a git clone to
get the code to my machine, uploaded my SSH key, and now I
On Fri, Jul 08, 2016 at 08:47:29PM -0400, we recorded a bogon-computron
collision of the flavor, containing:
> > >
> > > %configure --without-graphicsmagick --with-rtree
> > >
> > >That seems BAD since we know that GraphicsMagick support is
> > > probably more reliable than say ImageM
On Fri, Jul 8, 2016 at 7:44 PM, Tom Russo wrote:
> On Fri, Jul 08, 2016 at 04:38:24PM -0700, we recorded a bogon-computron
> collision of the flavor, containing:
> >
> > Hello Tom,
> >
> > I'm working on updating my Xastir documentation for Centos here to now
> > use Github/Git vs. sf.net/CVS:
>
On Fri, Jul 08, 2016 at 04:38:24PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
>
> Hello Tom,
>
> I'm working on updating my Xastir documentation for Centos here to now
> use Github/Git vs. sf.net/CVS:
>
> http://www.trinityos.com/HAM/CentosDigitalModes/hampacket
Hello Tom,
I'm working on updating my Xastir documentation for Centos here to now
use Github/Git vs. sf.net/CVS:
http://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#19b.xastir
In doing that update, I noticed the current xastir.spec file which is
seemingly 13 years old
On Thu, Jul 7, 2016 at 9:31 AM, Tom Russo wrote:
> As announced a couple of months ago, Curt and I have been talking about
> moving
> Xastir version control over to github, and discontinuing use of sourceforge
> and CVS for hosting the main repository.
>
> There wasn't much feedback from the grou
As announced a couple of months ago, Curt and I have been talking about moving
Xastir version control over to github, and discontinuing use of sourceforge
and CVS for hosting the main repository.
There wasn't much feedback from the group about that, and yesterday we went
ahead and did it. The sou
