Package Details: xfce-theme-greybird 3.23.3-1

Git Clone URL: https://aur.archlinux.org/xfce-theme-greybird.git (read-only, click to copy)
Package Base: xfce-theme-greybird
Description: Desktop Suite for Xfce
Upstream URL: https://shimmerproject.org
Licenses: CC-BY-SA-3.0 AND GPL-2.0-or-later
Submitter: flan_suse
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 287
Popularity: 0.003867
First Submitted: 2011-02-02 15:41 (UTC)
Last Updated: 2024-01-22 01:00 (UTC)

Dependencies (8)

Sources (1)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 22 Next › Last »

flan_suse commented on 2012-05-16 21:54 (UTC)

@thestinger Before I upload any changes, how does this look: http://pastebin.com/gLhRqaFf It builds the package correctly, even with subsequent builds. However, this makes things a bit more complicated than they previously were. I even had to use different aliases at the top, since using the official _gitroot and _gitname overwrites the PKGBUILD with an updated pkgver number (against my wishes.) This is, after all, not a -git package, but a stable release. I just use git in the PKGBUILD because it is more flexible (users can use the master branch or any branch of their choice), and there were random server issues with the tarballs on their github in the past. Let me know what you think. I will also make the same changes to my other Shimmer Project PKGBUILDs.

thestinger commented on 2012-05-16 02:34 (UTC)

@flan_suse: in build(), you should do the clone like it's done in /usr/share/pacman/PKGBUILD-git.proto, which won't have to re-fetch the sources if you're just rebuilding and will just fetch deltas on an update if you've kept the package sources around. You can skip making a "$srcdir/$_gitname-build" directory though because you don't need to build anything. In package(), replace the clone with copying over the git repository from "$srcdir" and leave the rest as it is or just copy over the files that are needed (either works).

flan_suse commented on 2012-05-16 01:49 (UTC)

@thestinger I'll try that out tomorrow if I have the free time. It makes sense from how you've described it. I just always viewed build() to be reserved for actual compiling, and I never considered pulling from a git repository to fall under the compile/build category. "...so the package can be rebuilt (or just repackaged) without fetching the source again." I never knew that it made a different when using git. So you mean to say that if I place the git clone and checkout in build(), any subsequent runs of makepkg will skip this part? Not sure if I interpreted it 100%. @Math In the meantime, let me know if yaourt works (even with multiple builds), since I just tried it out with no issues. When I test my PKGBUILDs with makepkg, I always start with a clean build directory.

thestinger commented on 2012-05-15 19:09 (UTC)

@flan_suse: you should use a separate build directory like the prototype PKGBUILDs though (/usr/share/pacman). The clone (and probably the checkout too) belong in a build() function (checking out to "$srcdir") and then copying to "$pkgdir" in package() so the package can be rebuilt (or just repackaged) without fetching the source again.

<deleted-account> commented on 2012-05-15 19:04 (UTC)

@flan_suse Thnx for your reply. I'm just using makepkg, but I'll see what yaourt can do for me. :)

flan_suse commented on 2012-05-14 23:43 (UTC)

@Math How are you building the package? Are you using a helper (e.g, yaourt), or are you manually using makepkg? Yaourt automatically starts with a clean build directory, so I never get such a problem.

<deleted-account> commented on 2012-05-14 19:12 (UTC)

I'm getting this error: error: Your local changes to the following files would be overwritten by checkout: README gtk-2.0/gtkrc gtk-3.0/gtk-widgets.css gtk-3.0/gtk.css metacity-1/metacity-theme-1.xml Please, commit your changes or stash them before you can switch branches. Not sure what to do, maybe someone can help.

flan_suse commented on 2012-05-03 19:57 (UTC)

@txus I tried out LightDM (lightdm-gtk-greeter), and I got it to work with the below steps to use the Greybird theme and wallpaper. It looks nice, and it's not too cluttered. It also looks much better than GDM, that's for sure. I bumped into some problems: * For some reason it requires accountsservice and libsystemd. ("Light" DM, eh?) * Because of this, it ignores the users.conf options, and it displays the "lightdm" user in the login list. * The buttons on the upper-right (accessibility and power) are buggy. Sometimes they are delayed, and sometimes you must click them repeatedly to display the drop-down options. (Might only be a bug with lightdm-gtk-greeter, though.) * The "Computer" icon has no easily discoverable way to change it. I found out how to, in the Wiki page, and I changed it to an Arch logo. (Could have been easier.) All in all, LightDM seems to be useable, and it looks great with the Greybird theme and wallpaper! Would be interesting to play around with the other greeters, such as lightdm-unity-greeter. For now, though, I am switching back to XDM and the Arch XDM theme. I don't doubt this login manager will improve with time, especially since it is the default for Ubuntu and Xubuntu.

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 22 Next › Last »