Re: [Xastir-dev] [Xastir] Xastir development source now on github, sourceforge CVS now closed to new commits.

On Thu, Jul 07, 2016 at 02:12:10PM -0500, we recorded a bogon-computron collision of the flavor, containing: > Just trying it out -- checked out the repo, bootstrap.sh, ./configure, make > > Unfortunately: > > make[2]: *** No rule to make target `README.CVS', needed by

Re: [Xastir-dev] Compiling from "build" directory

On Mon, Apr 15, 2019 at 12:51:01PM -0700, we recorded a bogon-computron collision of the flavor, containing: > On Mon, Apr 15, 2019 at 10:03 AM Tom Russo wrote: > > > > On another note, I'd really like someday to do away with our "internal > shapelib" > > because it's an artifact of the bad old

Re: [Xastir-dev] Github README

On Tue, Apr 16, 2019 at 08:35:30AM -0700, we recorded a bogon-computron collision of the flavor, containing: > I was thinking about that github:xastir/Xastir page in terms of a > first-time user: They want instructions for compiling and getting it > running RIGHT NOW. They don't care about 95%

Re: [Xastir-dev] [Xastir] ATTENTION: Preparing for next release: Please thrash on the code

; > On Thu, May 30, 2019 at 12:38 PM Curt Mills wrote: > > > Rgr. Will post announcement today then. > > > > On Thu, May 30, 2019 at 10:33 AM km5vy Tom Russo > > wrote: > > > > > On Thu, May 30, 2019 at 11:12:03AM -0600, we recorded a bogon-comput

Re: [Xastir-dev] [Xastir] ATTENTION: Preparing for next release: Please thrash on the code

before telling Xastir about the images (using GDAL command line tools). > On Fri, May 31, 2019 at 2:43 PM km5vy Tom Russo wrote: > > > On Fri, May 31, 2019 at 02:29:36PM -0500, we recorded a bogon-computron > > collision of the flavor, containing: > > > So, a question. I'

Re: [Xastir-dev] [Xastir] ATTENTION: Preparing for next release: Please thrash on the code

On Mon, May 27, 2019 at 11:52:53AM -0700, we recorded a bogon-computron collision of the flavor, containing: > Fine by me. I can do all the announcements. It is likely that I'll go ahead and walk through the git steps of doing the release tonight instead of tomorrow. My "friday off" turns out

Re: [Xastir-dev] Editor header in source files

On Tue, Apr 30, 2019 at 11:14:54AM -0700, we recorded a bogon-computron collision of the flavor, containing: > What do you think of this idea instead: https://editorconfig.org/ > It requires a plug-in for Emacs and VIM, but we could add that to the > coding standards. I'm not particularly keen

Re: [Xastir-dev] Editor header in source files

On Tue, Apr 30, 2019 at 12:41:50PM -0600, we recorded a bogon-computron collision of the flavor, containing: > On Tue, Apr 30, 2019 at 11:14:54AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > What do you think of this idea instead: https://editorconfig.org/ >

Re: [Xastir-dev] Editor header in source files

Seconded. I think that the people who established the current standard for Xastir are long gone, and maintaining consistency with that style for the sake of consistency has gone on long enough. I personally hate *both* the four-space indentation *and* the "egyptian brace"/K style, and prefer

Re: [Xastir-dev] Travis-CI: gcc 8?

On Tue, Apr 23, 2019 at 08:35:12PM -0700, we recorded a bogon-computron collision of the flavor, containing: > Your thinking on distributions to drop is sound. It's what I would want as > well. > > For the gcc-8 build should we add those two flags as well? Perhaps, unless you really want to

Re: [Xastir-dev] Git question

y, since your commits were mooted in upstream. > On Mon, Apr 22, 2019 at 9:33 AM km5vy Tom Russo wrote: > > > On Mon, Apr 22, 2019 at 09:28:14AM -0700, we recorded a bogon-computron > > collision of the flavor, containing: > > > However I didn't rebase. I only di

Re: [Xastir-dev] [Xastir] Fwd: Bug#957970: xastir: ftbfs with GCC-10

On Fri, Apr 17, 2020 at 08:54:30AM -0700, we recorded a bogon-computron collision of the flavor, containing: > Sure. I can do that tonight if we're all in accord. It's a fairly lightweight process anymore to push out a release on github. > On Fri, Apr 17, 2020 at 8:33 AM Tom Russo wrote: > >

Re: [Xastir-dev] Maybe it's time for a 2.1.8 release?

I have created a pull request on github with the changes needed to documentation to implement this simplified release process. When you and Curt have reviewed it, please merge it and I'll move with actually doing the point release. Doing the point release this way is very little more than

Re: [Xastir-dev] Switching string length discussion to here

On Sun, Dec 19, 2021 at 02:37:24PM -0800, we recorded a bogon-computron collision of the flavor, containing: > Ah, should have read everything more thoroughly... So by adding > another library to Linux we might be able to use something better. I disagree: by adding another library, we're