Re: [aur-general] Fwd: Re: How do I show a AUR Rebuild as a newer build?
‐‐‐ Original Message ‐‐‐ On Monday, October 22, 2018 11:47 AM, Tinu Weber wrote: > More generally, however, what would be the best approach to applying > downstream/user-specific changes without breaking the versioning? The > ones I know all have some issue: > I must be misreading this, because I don't see why you shouldn't use the exact same pkgver/pkgrel as the original package? If you want to port the modified package to the subsequent pkgrel or pkgver, you can always put the package on hold or figure out another way to be aware of . I think what we should be thinking about is to actually make it easier to serve this need in pacman itself somehow, if there isn't already a practicable way. There seems to be a way to list packages to upgrade before -Syu, IIRC. If you added an obvious modification to your package or something similar, the dumb (admittedly maybe, not always easily debugged) way to notice that you overwrote a local modification is when it's gone... cheers! mar77i
Re: [aur-general] intellij-idea-community-edition
> (I'm not sure whether I'm posting to the correct mailing list.) > I'm a happy user of IntelliJ IDEA. Unfortunately, the community > package intellij-idea-community-edition is out-of-date most of the > time. As of writing, it has been updated at 2018-07-10 and flagged pycharm-community user here (which is on AUR). I have a PKGBUILD in ~/abs, where I just add the most recent version number and update the checksum when pycharm notifies me that there's a new version. Not relying on other ever-broken carbon-based lifeforms is fine with me. ;) cheers! mar77i Sent with ProtonMail Secure Email.
Re: [aur-general] upgrade of "conf.d/*.conf"-style packages containing example configs
‐‐‐ Original Message ‐‐‐ On May 31, 2018 10:00 PM, J. Konrad Tegtmeier-Rottach via aur-general wrote: > Hi, > I've run into a general issue with software packages that use a > configuration directory, aggregate configs therein using a glob rule > on the filenames, and contain an example config. > An example is `community/consul`, which > > - globs for `/etc/consul.d/*.{hcl,json}` > - contains `/etc/consul.d/example.json` > > When I configure these types of software first I delete the example > file, and then place additional configs in that directory, with > everything working as expected. > Then an upgrade for that package rolls around, and the example config > is recreated. This usually means that as soon as the software reloads, > the recreated example config gets loaded, too, and the software tends > to fail or behave in byzantine ways. > As a rule of thumb, if a software package ships an example config, it should IMO not be made effective on installation, unless it's "generally applicable or useful" in that it then needs only minor edits for each particular use case. You can see how this definition on its own makes room for interpretation already, though. My guess is that a package that breaks due to re-shipping its own example configuration qualifies for a bug. Many software packages (systemd is taking the cake today) ship their example configuration somewhere in /usr, which seems a better idea, because there they don't accidentally become effective. Oftentimes these problems occur due to ignorant or uninformed upstream which would benefit from people like you who are reporting these problems. That said, are you interested in finding more of these packages? I can think of a wonderful role for you around here. cheers! mar77i Sent with ProtonMail Secure Email.
Re: [aur-general] Please remove gsmartcontrol-svn package from AUR
Original Message On February 14, 2018 3:46 PM, Simon Doppler do...@dopsi.ch wrote: >On Wednesday, 14 February 2018 15:29:29 CET Eli Schwartz via aur-general >In this case, he should not publish the development code anyway, since nothing > will stop users from submitting bug reports for development code (whether it > is mail based bug reporting, mailing list based, using Git{hub,lab,*}-style > issues or an actual bugtracker). >Simon Doppler (dopsi) > E: do...@dopsi.ch > I seriously wonder, though. How *do* you so consistently break things between releases? cheers! mar77i Sent with ProtonMail Secure Email.
Re: [aur-general] Moving xss-lock to community
Original Message On January 19, 2018 11:52 AM, David Rungewrote: >Fwitw (and sorry for hijacking), I recently tried xprintidle (with a forked >upstream, different from the one in the AUR) and it seems to work. > This might still be used in a script to lock screens automatically under X, > but it's clunky. I'd much prefer a more complete solution, as xautolock is > aging (not so well) and at least in my case produces undesirable defuncts > from time to time. > xss-lock seemed too broken at that time, so I never used it. > Are there any other alternatives not mentioned in the wiki? I wrote xidle_dispatcher [0] myself, which I basically hook up to slock. Another tool I know of does basically the same thing, both being more or less what xssstate.c[1] does. cheers! mar77i [0] https://github.com/mar77i/xidle_dispatcher [1] https://git.suckless.org/xssstate/tree/xssstate.c Sent with ProtonMail Secure Email.