Package Details: sddm-archlinux-theme-git 0.1.r13.ge2054bd-1

Git Clone URL: (read-only, click to copy)
Package Base: sddm-archlinux-theme-git
Description: Archlinux Theme for SDDM
Upstream URL:
Licenses: CCPL:cc-by-sa
Submitter: bchretien
Maintainer: Scimmia
Last Packager: Scimmia
Votes: 67
Popularity: 0.000000
First Submitted: 2013-12-17 13:07 (UTC)
Last Updated: 2018-02-21 18:53 (UTC)

Latest Comments

ArthurBorsboom commented on 2015-07-08 08:48 (UTC)

Jul 08 10:45:33 pb450 sddm-greeter[2174]: file:///usr/share/sddm/themes/archlinux/Main.qml:190:13: QML Row: Cannot specify left, right, horizontalCenter, fill or centerIn anchors for items inside Row. Row will not function.

mouseman commented on 2015-04-06 07:53 (UTC)

Thanks for this theme. I just centered the fields to suit my preference. Is it possible to clear the password field after an incorrect login attempt?

Scimmia commented on 2015-01-13 02:10 (UTC)

There isn't a release, so I can't make a release package. If the upstream developer tags a release, it would be no problem.

ArthurBorsboom commented on 2015-01-12 20:59 (UTC)

Hi Doug, First thanks for creating and maintaining this package. I have a favor to ask. Would you mind to create a non-development package (non git) of this package in AUR? For example sddm-archlinux-theme v0.1 instead of sddm-archlinux-theme-git.

Scimmia commented on 2014-10-12 18:06 (UTC)

It works because you probably already have git installed. Try building in a clean chroot and watch things fail. And the install command in that PKGBUILD only installs one file. You can use the -D switch to automatically create the dir when installing one file, but it doesn't work when installing multiple files. The install command does not work on directory structures, either, so you can't just install a dir.

flamusdiu commented on 2014-10-12 17:56 (UTC)

Here's a PKGBUILLD from git: However, somehow that works even though the wiki says this: Include the appropriate VCS tool in makedepends=() (cvs, subversion, git, ...). I stand corrected. =\ If it works without it, then why does it need to be included in the first place? #firstworldproblems Actually, I did it based on another package (I wasn't at home.). I'll check it maybe, I did the install format incorrectly. Let me see.

Scimmia commented on 2014-10-12 05:19 (UTC)

git most certainly does need to be in the makedep array. It's needed to build the package. Even the wiki says it needs to be included. The current pkgver function pulls an actual version number. It's set up as is preferred according to the wiki, just not as the examples. Guidelines are just guidelines, this is better. It's specific to this package, not something generic for people who don't want to think. Did you actually try your package function? It does nothing besides create a an empty directory (note that's a directory, there's no such thing as a folder in *nix).

flamusdiu commented on 2014-10-12 02:07 (UTC)

I would change the PKGBUILD to this to better support Arch Linux guildlines: _pkgname=sddm-archlinux-theme pkgname=$_pkgname-git pkgver=0.1.r11.8898d77 pkgrel=1 pkgdesc="Archlinux Theme for SDDM" arch=('any') url="" license=('CCPL:cc-by-sa') depends=('sddm') install="$_pkgname.install" source=("git+$_pkgname.git") sha256sums=('SKIP') pkgver() { cd "$pkgname" printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" } package() { cd "$srcdir/$_pkgname/archlinux" install -dm 644 "$pkgdir/usr/share/sddm/themes/archlinux/" } You don't need to have "git" in the makdepends array. It already checks that if you use a "git" source. Also, change the package version function from off the Wiki site to better match what is expected (and cleaner as well). Fixed the installation, since you can install the folder and all files at the same time as creating the folder. =)

Scimmia commented on 2014-09-18 16:25 (UTC)

That works, too. It could use some simplification.

bchretien commented on 2014-09-18 16:23 (UTC)

@Scimmia: or "sddm-git" doesn't work with mine. But well, since I'm not even using this package anymore, you can adopt it and update it.

Scimmia commented on 2014-09-18 16:19 (UTC)

Strong reason? How about that your package doesn't work with sddm-git? Seems pretty strong.

bchretien commented on 2014-09-18 16:17 (UTC)

@Scimmia: "supposed to be paying attention", exactly. People are also supposed to abide by the law, yet prisons are full ;-) I guess we have 2 different point of views here: "being overzealous/overcareful for future packages/modifications and trying to prevent careless users from shooting themselves in the foot" vs "blindly trusting the users to do the right things and keeping things simple". I used to agree with you, but I ended up changing my mind after seeing that many users did not fully understand what installing VCS packages implies (especially when some programs only have a VCS package in the AUR). If you can give me a strong reason to change that (other than the philosophical differences that we may have already discussed), I will. In the meantime, it actually helped some people making the transition to the new AUR sddm packages.

Scimmia commented on 2014-09-18 15:47 (UTC)

@bchretien, you have a gross misunderstanding of VCS packages. The user is supposed to be paying attention to upstream when using them and doing their own updates. Users who use VCS packages and rely totally on a AUR helper to tell them when to update are doing things very wrong that that is their own fault. As for two versions being available, that's true, but they both satisfy your version requirement, so that arguement is moot.

bchretien commented on 2014-09-18 15:37 (UTC)

@Spyhawk: the issue with VCS PKGBUILDs is that they don't need to be updated at every commit. Most of the time, maintainers leave them as is, even after new releases with API/ABI/file structure breaking changes. Users are not noticed and they need to remember updating their VCS-based packages. Take the following example: sddm 0.10.0 breaks their file organization again. "sddm" is updated to 0.10.0, and the themes are updated without any version requirements. So everything works fine for "sddm" users, but users that installed "sddm-git" are not noticed, they updated the themes as suggested by the AUR helpers, and they end up not being able to login with their favorite sddm theme. It all comes down on the sddm-git maintainer. Most maintainers do their job with a bump when there's a new release, but it's far from being a rule of thumb on the AUR. That's a problem I encountered several times with other packages I maintain(ed), and having the explicit versions made things much easier for both users and maintainers. This is even advised in the guidelines available on the Arch Wiki: Thus, if there's a problem with the VCS version, the user is warned when building the package, not when he's booting his system. Another example: they add a new commit to master that break these themes (or other hypothetical packages that depend on it). If sddm-git's PKGBUILD is fixed, then we can simply add an extra check in the themes, else the sddm-git users can't be warned. I also know some people who don't rely on AUR helpers (I find it crazy and don't really get why, but that's a fact...). Although, "forcing" them to choose an helper by making things more complicated for them is tempting, indeed. @Scimmia: you can do both, these are not exclusive. And there's nothing preventing people from adding extra versions of sddm later on. Technically, there's already 2 available.

Scimmia commented on 2014-09-18 15:09 (UTC)

It's correct, but providing <pkg>=$pkgver is correct, too. That said, the problem really is the totally unnecessary version requirement here. Version requirements are only useful if more than one version is available either in the repos or in the AUR. Since that's not the case, you're just making problems.

bchretien commented on 2014-09-18 14:49 (UTC)

@Spyhawk: once again, it is possible to install it with sddm-git as long as the PKGBUILD is fixed (I commented twice on the package already, still waiting for a reaction of the maintainer). I just tested, and it works smoothly.

bchretien commented on 2014-09-18 14:29 (UTC)

@Spyhawk: except that AFAIK, AUR helpers do not warn you if a package disappeared from the AUR when updating (at least not yaourt), which is what happened to sddm-qt5. Moreover, some Arch-based distributions could be using the previous release for a few days before making their update. If there is some missing information in a PKGBUILD, then this PKGBUILD should be fixed. Not the ones that depend on it.

bchretien commented on 2014-09-18 09:28 (UTC)

@Scimmia: actually, sddm-git should provide $_pkgbase=$pkgver. I added the >=0.9.0 check because they changed the location of files in that release, so this package requires that minimum version. Also, since sddm packages have been reorganized in the AUR, people with sddm-qt5 were not notified (since the package has been removed), and blindly updating the themes without the version check would likely break things for them.

Scimmia commented on 2014-09-18 07:19 (UTC)

The version requirement on the sddm dependency isn't necessary. There are no versions older than 0.9.0 available. Further, it doesn't work with sddm-git right now since it provides sddm, not sddm=$pkgver.

bchretien commented on 2014-03-29 17:33 (UTC)

@habarnam: done, thanks ;-) @absturztaube: done as well!

absturztaube commented on 2014-03-29 17:28 (UTC)

Please change the upstream url to the github repo thx

habarnam commented on 2014-03-29 13:40 (UTC)

I had some changes accepted by the theme creator to allow displaying the theme in the KDE sddm configuration module. I have updated the PKGBUILD[1] to accomodate for these changes and added a real pkgver() function. [1]

bchretien commented on 2014-02-05 10:19 (UTC)

@Etzos: except this wouldn't work with "sddm" since this theme relies on Qt5 features. The problem is that "sddm-qt5-git" should provide "sddm-qt5", not "sddm".

Etzos commented on 2014-02-05 06:55 (UTC)

Please change the dependencies to "sddm" instead of "sddm-qt5" that way the development version of sddm can be used without having the modify the PKGBUILD.