Re: stable search

Nathan Willis <[email protected]>
Newsgroups gmane.comp.fonts.fontforge.devel
Message-ID <CAAL6+1L07RHtv0afh-_GkWTEU2ixWaN2dWMpRhjhuws_Fuk3oQ@mail.gmail.com>
On Fri, Nov 15, 2013 at 1:00 PM, vernon adams <[email protected]>wrote:

>
> On 15 Nov 2013, at 10:10, Nathan Willis <[email protected]> wrote:
>
> > Friends, romans, countrymen,
> >
> > ...So try as I might, I haven't been able to find a commit from any time
> in the past three or four weeks that won't segfault on me (well, on my
> SFDs, to be more precise).  Does anybody have a personal recommendation for
> the last period of relative stability?  I'm really not interested in the
> collab features, so I can compile without those, but I've been trying to
> step back to (for example) before the multichar stuff started going in.
>  Haven't quite found it yet.
> >
> > Vern, on issue 945 you said you only started seeing class-based kerning
> crashes in "the last few" pulls -- what was the most recent one you didn't
> have trouble with?
>
> Not sure exactly which commit that would have been. You would have to try
> those from about a 6-7 days ago. however, I have (so far) found that the
> latest commits, from fbda480a5733c619a0b45dcf37cfd7bde06bd53f on, have not
> repeated the same issues that led me to report bug #945. A serious
> SFD-related bug was definitely fixed by
> 2493cba30c60d9296902150a683c04c8b2319177, but still could be related bugs
> still lurking. I worked all day yesterday in fontforge (both OSX and
> debian) without problems with my SFD files, but… you didn’t :) so it would
> be good if you could reproduce your crashes and report it. Feel free to
> send me any offending SFD too, i am happy to look at it and report whatever
> issues i find with it.
>
>
Thanks V.   I had pulled yesterday morning, so fbda480a57 is probably where
I was.  I haven't been able to track down the precise SFD problem yet,
since I don't have any test files, just the ones I'm supposedly working on
(which are big).  But soon; I have saved gdb backtraces from the current
$HEAD crashes ever since I saw that they were repeatable.  Right now I'm
just trying to build something I can stick with.


> >
> > I'm really just interested in updating my local version to the nicer
> editing/canvas/UI stuff; otherwise I've been happy with my vintage 2012-era
> build --- classic lines and all. The other features are cool, but not
> nearly as big a part of my daily workflow…..
>
> I sympathise with this. As much as i back the recent changes and the
> direction they are going, i still think there’s a very good reason for
> ‘harvesting’ a branch of what you describe as ‘vintage 2012 era’ fontforge,
> leave it as a ‘stable release’ , whilst the development continues on, as it
> is doing, at the tip of the project.
>

Yeah, back in the ol' days <scratches long gray beard>, rolling a release
was common practice.  It looks like the gh Milestones are dead & gone,
though.  I sort of feel like there are more than enough significant
features already to pin down a 2.0 non-"beta".  Not that the actual number
means anything....


> On a related subject; it’s a real shame that the sortsmill fork is such an
> impenetrable beast to build from latest source, for us pedestrian software
> users.
>

Wow, I haven't even tried, at least in recent memory.

Nate

-- 
nathan.p.willis
[email protected]
identi.ca/n8

------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk

_______________________________________________
Fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.