Re: Do we want versioned symbols in ncurses?

Thanks for the quick turnaround. > Debian has identifier some potential problems, quoted from > : Ah, yes. The version script also sets a bunch of symbols to local scope. Good catch. Off the top of my head, the only sanity-check I can

Re: Do we want versioned symbols in ncurses?

B. Wilson schreef op di 12-04-2022 om 12:04 [+0900]: > I ran into this after encountering a project that explicitly uses ncurses > symbol versions. FWIW, there will only ever by one ‘version’ of a symbol, according to upstream:

Re: Do we want versioned symbols in ncurses?

B. Wilson schreef op di 12-04-2022 om 12:04 [+0900]: > Hey Guix, > > Is there any particular reason why our current ncurses packages builds without > versioned symbols? Upstream specifies only default versions (i.e. via @@), no > forced ones, so IIUC that should make the library drop-in

Do we want versioned symbols in ncurses?

Hey Guix, Is there any particular reason why our current ncurses packages builds without versioned symbols? Upstream specifies only default versions (i.e. via @@), no forced ones, so IIUC that should make the library drop-in replaceable for everything we have so far. Am I missing something?