From: bm16ton <bm16ton@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Modify ncurses package to provide libtinfo
Date: Sun, 15 Oct 2023 01:59:52 +0200 [thread overview]
Message-ID: <20231014235952.f-o5Rixe9JxI_wKGx9TvwHL2EqM2XxKlN0lugDcS6NI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11718@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
New comment by bm16ton on void-packages repository
https://github.com/void-linux/void-packages/issues/11718#issuecomment-1763213557
Comment:
I know posting to old threads in forums is considersd rude but it seems like github issues maybe different? If not I truely apologize. Just wanted to say after playing with ncurses crosscompiling for niche hardware and googling I found this and now I think I'm gonna try void linux! (never heard of it b4 just now) Mostly been using homebrew "distros" for past couple years and its always been if the app needed symbols from a specific lib I would point to that lib in Makefile etc for linking all is good even if 2 libs had same symbol. But based of the little I can gather from here if a second lib with same symbol is available then the pkg management being used to compile will fail? Either that or instead of having 2 libs same symbol you dropped one of them and the old now missing lib is what's specified so it fails? Wasn't enuff here for me to get a firm grasp, but its got me curious so I'm gonna give it a go! Package management is such a huge, complicated, endless variation of things, concept that its fun to explore and learn how people greatly (and I do mean greatly!) smarter then myself has implemented it! Hopefully ill be able to gather some reasoning behind its various design decisions from docs and commits, and hopefully be a better programmer from it..Thank you guys ooensource contributors are truely my heros and seldom praised enuff imho
prev parent reply other threads:[~2023-10-14 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11718@inbox.vuxu.org>
2020-01-31 0:56 ` voidlinux-github
2020-01-31 0:56 ` voidlinux-github
2021-12-06 19:14 ` hasufell
2021-12-06 20:06 ` [ISSUE] [CLOSED] " q66
2023-10-14 23:59 ` bm16ton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231014235952.f-o5Rixe9JxI_wKGx9TvwHL2EqM2XxKlN0lugDcS6NI@z \
--to=bm16ton@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).