Package Details: ncurses-git 6.2.20200919.r0.gfceb2b7d-1

Git Clone URL: https://aur.archlinux.org/ncurses-git.git (read-only, click to copy)
Package Base: ncurses-git
Description: Screen handling and optimization package
Upstream URL: https://invisible-island.net/ncurses/ncurses.html
Licenses: MIT
Conflicts: ncurses
Provides: libformw.so, libmenuw.so, libncurses++w.so, libncursesw.so, libpanelw.so, ncurses
Submitter: Chocobo1
Maintainer: Chocobo1
Last Packager: Chocobo1
Votes: 1
Popularity: 0.53
First Submitted: 2020-01-12 12:22
Last Updated: 2020-09-21 15:54

Dependencies (2)

Required by (994)

Sources (1)

Latest Comments

1 2 Next › Last »

shoober420 commented on 2020-09-21 20:02

I’m just looking out for people, and want us all to an optimal package. Thank you very much for the consideration. It’s best to be on the safe side.

Chocobo1 commented on 2020-09-21 15:43

Unless of course, the Arch guys felt otherwise, but they would of enable it by default of course. But they don’t, so you shouldn’t allow it possible either.

This package and the official one are not exactly the same as I said before.

There may just very well be a important reason ada is disabled for ncurses, especially since it’s explicitly set to build without ada.

You always bring up the Arch guys decision, but have you found out why exactly they added that flag? No point is made in pure speculation, so no guessing please.

Why would you risk a user running in to trouble? What if there’s a bug with ada support? What if it’s bloat? If it explicitly builds without ada, it would be wise to do the same.

Good, more hypothetical questions... Are you using ada? No? Then I guess can't represent those who are actually using ada. I think now I've found a good reason to add that flag since that would help ease you of your fear of those hypothetical issues.

shoober420 commented on 2020-09-21 13:36

The AUR is also a community effort. We need to keep in mind others who will use the package, instead of being selfish. The “Speak for oneself” attitude is that of a Gentoo user, where he compiles and tweaks everything himself. He doesn’t need to worry if he accidentally enabled ada support on a unknowing user. You have to keep others in mind. You need to make PKGBUILDs with everyone in mind, not just yourself.

shoober420 commented on 2020-09-21 13:03

Running old and/or different build flag schemes on git packages can be more dangerous, so it’s most wise to at least use the build flags from the latest official PKGBUILD. You’re literally asking for trouble when differing build options in the whole Arch environment.

I requested to have ipv6 disabled from xserver a while back. It’s not used a lot yet, and is a security concern. You know what else is a security concern? Differing build options. If a user wants to use ada, he can enable it himself, just as I disabled ipv6 manually. If I need to make a “ncurses-noada-git”, I can do that.

It wouldn’t be respectful to the user to sneak in ada support in their ncurses package, simply because they had ada installed. Unless of course, the Arch guys felt otherwise, but they would of enabled it by default of course. But they don’t, so you shouldn’t allow it possible either.

There may just very well be a important reason ada is disabled for ncurses, especially since it’s explicitly set to build without ada. Why would you risk a user running in to trouble? What if there’s a bug with ada support? What if it’s bloat? If it explicitly builds without ada, it would be wise to do the same.

Chocobo1 commented on 2020-09-21 07:09

Just because it might not trip for me, doesn’t mean it won’t trip for someone else.

One should only speak for oneself, what if someone actually do want the ada bindings and make a request for it? Should you deny his request? Note that having ada bindings does not harm this package usability in any way.

There is absolutely no reason to risk having these settings changed because of a user setup and/or the default build options updated.

Of course it would make sense to update the build flags when upstream changed, note that we are dealing with latest development git branch, not the stable releases. If you are concerned that -git packages would causes instability then you probably should stick to official packages instead, -git packages are not guaranteed for being stable but are good for trying out the latest features.

shoober420 commented on 2020-09-21 06:39

This is not just about me, this goes for anyone who compiles your package. Just because it might not trip for me, doesn’t mean it won’t trip for someone else. There is absolutely no reason to risk having these settings changed because of a user setup and/or the default build options updated.

Chocobo1 commented on 2020-09-21 06:20

If the following build flags were truly redundant, they wouldn’t be included in the official repo PKGBUILD.

Let's look at them one by one before jumping to conclusion too quickly...

--with-normal (installs static libraries)

This option is default ON as stated by the output of ./configure --help:

--with-normal generate normal-libraries (default)

--without-ada (if the ada programming language was that important, Arch wouldn’t disable it)

In the case of this flag absent, the configure script will search for ada and if it is not found then nothing will be done (basically no-op). If you do have ada installed and this behavior trips you in some way then I'll add it.

--with-cxx-binding (c++ binding sounds important, the Arch guys think so too).

The output of ./configure only lists the opposite flag --without-cxx-binding. I suppose building c++ binding is already the default action, please correct me if I'm wrong.

UPDATE: This is from the output of the configure script: checking if you want to build C++ binding and demo... yes. So my guessing was right, it is enabled by default.

If you don’t match the build options from the official repos, your packages can end up being buggy since other packages and system components within Arch may be expecting them to be set, especially if they are set in the official PKGBUILD.

Yes, I'm aware of this. As explained above, I think the only (slightly) controversial flag is --without-ada, let me know if it really trips you in some way then it is justified to add it.

shoober420 commented on 2020-09-21 06:08

If the following build flags were truly redundant, they wouldn’t be included in the official repo PKGBUILD.

--with-normal (installs static libraries) / --without-ada (if the ada programming language was that important, Arch wouldn’t disable it) / --with-cxx-binding (c++ binding sounds important, the Arch guys think so too).

If you don’t match the build options from the official repos, your packages can end up bugging a system out since other packages and system components within Arch may be expecting them to be set, especially if they are set in the official PKGBUILD. You’re only asking for trouble using different build options.

If you’re going to drastically change build options, change the name of your package. For example, since you want ADA programming language for what ever reason, name this “ncurses-ada-git”. This is why I personally have “minimal” and “nosystemd” variants of packages I maintain.

Chocobo1 commented on 2020-09-21 05:44

Your build options are simply out of date.

Which part? please be specific.

The official repo package would not of added them for no reason.

I consider some configure flags redundant in there.

shoober420 commented on 2020-09-21 05:35

Your build options are simply out of date. The official repo package would not of added them for no reason. It’s good practice to keep up to date with the official repo PKGBUILDs, and use them as a template. Reason being, your build options are old. wlhlm knows this as well, as he commented the same thing.