My two cents: As a developer working on my first pkgsrc package (WIP), I would likely seek assistance on the pkgsrc-users or tech-pkg mailing lists, as those are frequented by people who have encountered similar issues, or perhaps in the Libera IRC #pkgsrc channel.
Regards, Kami On Wed, Nov 19, 2025 at 2:20 PM Greg Troxel <[email protected]> wrote: > Ramiro Aceves <[email protected]> writes: > > > I also think that if some packages aren't in pkgsrc, it's because > > someone has already tried and porting them is impossible or too > > difficult. > > I think that is not a correct assumption. Another reason is that nobody > has tried. > > > I often examine the Makefiles of existing packages and think, "Wow, > > that's complicated." I'm also amazed at the number of patches. Some > > packages have just a handful, but others, like Chromium, have > > hundreds. > > That's mostly not about pkgsrc. Lots of patches is usually because the > upstream code has portability problems. > > > Some things get very complicated, but packages that have normal build > systems and don't have portability problems are often fairly simple. > > I think after you get used to things you will find that most of the > effort is dealing with upstream complications. > > But really: feel free to start creating a package in wip, even if it's > got a bunch of comments instead of make code. Look at other pkgsrc > entries for inspiration. >
