| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Where before could be found the compatible GNOME Shell version number is
now the intended Ubuntu version. The number sought fortunately still
resides in the description text.
|
|
|
|
Having the version readily available means that multiple functions in
the PKGBUILD can use it without extracting it again every time.
Unfortunately, makepkg escapes DLAGENTS in a way that makes adding a
complex one quite ugly: It splits arguments on free spaces, so all
spaces in the quote-enclosed argument to "bash -c" have to be escaped.
On top of that, there are many sed expressions and even sed expressions
in sed expressions containing escaped symbols which now have to be
escaped again or even three times.
|
|
As it disappeared from the source archive content, the version prefix,
denoting the compatible gnome-shell version, became static to continue
counting versions without changing scheme.
The actual current version number can be extracted from the description
page of the theme, resurrecting it to its original meaning.
|
|
Instead of involving Dropbox, the source archive can now be retrieved
directly from GNOME-Look.org.
Packaging and version routine are adapted to the directory name that
does no longer include the gnome-shell version the theme applies to.
|
|
This reverts "attempt to fix ever-changing checksum".
Repacking the source was of no aid. It seems that indeed, small changes
to the archive content occur without a release.
It can still be speculated that these changes are introduced through
some internal Dropbox mechanism. As the archive is now distributed via
GNOME-Look.org directly, it is tempting to hope that this may make the
problem vanish.
|
|
|
|
This reverts "add mksrcinfo header".
The .SRCINFO is now generated by "makepkg --printsrcinfo" which does no
longer include any header since commit f63854f [1], released with pacman
version 5.0.1.
[1]: https://projects.archlinux.org/pacman.git/commit/?id=f63854fa96f658ca5bdf2c21a1cd33cf4e3fbdbd
|
|
|
|
The checksum of the source archive often changes without any evident
modification of its content. At the moment, I can only speculate about
why that happens.
Perhaps Dropbox compresses the files on the fly changing the checksum of
the archive, but not the contents, whenever some detail of the
compression process changes.
Fortunately, bsdtar can re-compressing archives as part of a pipe. This
way, it can be inserted as a DLAGENT so that it does its work before
makepkg computes the checksum.
|
|
|
|
The archive hash changed without any significant change to its contents,
so version in terms of pkgver and pkgrel remain unchanged, too.
Thanks to AUR user n0s3 for dropping a note about this.
|
|
This package provides themes for more than just gnome-shell. The package
name should reflect this.
|
|
This brings the text more in line with the original author's description
while explicitly mentioning all supported environments.
|
|
|
|
Inspecting other theme packages from the Arch Linux repositories, the
toolkits and applications that are themed are normally not listed as
dependencies. Only additional engines are hinted to as optional
dependencies for users of this subset of the theme.
|
|
Inspecting other theme packages from the Arch Linux repositories,
gnome-tweak-tool is normally not explicitly mentioned as there are other
means to apply a theme.
|
|
The packages gtk-themes-standard and gdk-pixbuf are transitifely
included via gnome-shell. The gtk-engines package is not needed at all
as the package works fine without it.
|
|
As there is no trace of a version number in the theme files themselves
apart from the compatible gnome-shell version, resorting to the
last modification time of any file at least provides some means to tell
apart releases.
|
|
It seems an update was released without a change in the date.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|