Re: [arch-general] Network manager package naming
On 2020/06/05, 14:25 Eli Schwartz wrote: > On 6/3/20 9:25 PM, LuKaRo wrote: >> Hi, [...] >> However, some packages have "network-manager" written with a hyphen: >> >> * network-manager-applet >> * network-manager-sstp >> [...] >> Can we simplify the naming conventions of those >> packages to use one common scheme that's easy to remember instead of >> having multiple coexisting ones? [...] > These are the upstream names of the relevant projects. So the "why" of > things is not hard to understand. > [...] One issue that could be fixed is adding "NetworkManager" to the description of e.g. network-manager-applet, and plasma-nm so that they can be found with a search for that name. -- ProgAndy
Re: [arch-general] Network manager package naming
On 6/3/20 9:25 PM, LuKaRo wrote: > Hi, > > there are several packages for network manager and related software in > the official repositories. Unfortunately, they follow different naming > schemes. Most packages have "networkmanager" written as one word: > > * networkmanager > * networkmanager-openconnect > * networkmanager-pptp > * networkmanager-vpnc > * networkmanager-strongswan > * networkmanager-openvpn > * ... > > However, some packages have "network-manager" written with a hyphen: > > * network-manager-applet > * network-manager-sstp > > And then there is > > * nm-connection-editor > * nm-cloud-setup > > which follows it's own naming scheme of having "networkmanager" redacted > to "nm". > > Unfortunately, that makes it hard to remember how each package is > called. Therefore there's always some guessing or searching involved > when installing a network manager related feature. Of course, this is > not the biggest issue of all time, but I think it's more complicated > than it should be. Can we simplify the naming conventions of those > packages to use one common scheme that's easy to remember instead of > having multiple coexisting ones? These are the upstream names of the relevant projects. So the "why" of things is not hard to understand. -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
Re: [arch-general] Network manager package naming
Hi, I noticed something similar going on with the KDE package groups. Some groups are named "kde-*" (e.g. kde-applications), some are named "kde*" (e.g. kdeaccessibility) and then there is one group that is simply called "plasma". Unfortunately I could not find any documentation about the naming scheme of the package groups. If I missed something I would be happy about a clarification as this seems very inconsistent and confusing to me. Best regards, Patrick 4. Juni 2020, 03:25 von li...@lrose.de: > Hi, > > there are several packages for network manager and related software in the > official repositories. Unfortunately, they follow different naming schemes. > Most packages have "networkmanager" written as one word: > > * networkmanager > * networkmanager-openconnect > * networkmanager-pptp > * networkmanager-vpnc > * networkmanager-strongswan > * networkmanager-openvpn > * ... > > However, some packages have "network-manager" written with a hyphen: > > * network-manager-applet > * network-manager-sstp > > And then there is > > * nm-connection-editor > * nm-cloud-setup > > which follows it's own naming scheme of having "networkmanager" redacted to > "nm". > > Unfortunately, that makes it hard to remember how each package is called. > Therefore there's always some guessing or searching involved when installing > a network manager related feature. Of course, this is not the biggest issue > of all time, but I think it's more complicated than it should be. Can we > simplify the naming conventions of those packages to use one common scheme > that's easy to remember instead of having multiple coexisting ones? > > Thanks a lot in advance, > > LuKaRo >
Re: [arch-general] community/NUT access cgi in /usr/share/nut/cgi without FollowSymLinks?
June 3, 2020 8:24 AM, "David C. Rankin" wrote: > All / Maxime, > > With the nut build option setting: > > --with-cgipath=/usr/share/nut/cgi \ > > when using apache with the default /srv/http/cgi-bin location, how > are you > supposed to access the cgi files in /usr/share/nut/cgi "Safely"? > > I have the entire /usr/share/nut/html directory protected by a dbm > database > file manipulated with dbmmanage, so to reach the you must > authenticate. That said, the only way I can make the cgi scripts work > is by > setting Options FollowSymLinks in the for "/srv/http/cgi- > bin" > after symlinking (e.g. ln -s /usr/share/nut/cgi /srv/http/cgi- > bin/nut) > > Is this safe? Is this intended way to provide access to the cgi > scripts? > > -- > David C. Rankin, J.D.,P.E. Hi David, I haven't used apache in years so please take this with a grain of salt. On nginx I'm using the alias directive, restricting access to the upsset.cgi to my local network [0], as suggested by the nut documentation in /etc/upsset.conf. It seems apache has a similar alias directive so you may be able to achieve the same without using any symlink [1]. [0] https://paste.xinu.at/BNUJFeuBycXUw8fB/ [1] https://httpd.apache.org/docs/2.4/mod/mod_alias.html#alias Cheers, -- Maxime
