| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The changes since the last .SRCINFO update were work in progress not
necessary providing a package possible to build at the moment of their
commit. Now that everything was at least tested a little and had time to
stabilize users should be notified about the update.
|
|
|
|
Recent releases are compatible to a series of gnome-shell versions. The
optdepends array should reflect this.
|
|
This theme is not only for gnome-shell. Releases are by necessity
roughly aligned with gnome-shell updated, but recent archives support
multiple different versions, which cannot properly mapped to a release
version number. As the time stamp recently became expressive enough to
tell versions apart, it suffices as a pkgver.
|
|
As the time stamp is quite detailed and the author in fact does
sometimes upload multiple revisions in one day, including the time
component helps telling versions apart.
Should the provided precision decrease some day, zeros can be padded to
keep version comparison consistent.
|
|
The meta data contains an upload time stamp. It is much easier to use
than finding the latest date from all the files.
|
|
As one of the checksums is now hidden in a function on purpose, the
standard updpkgsums would destroy the PKGBUILD. Here is an alternative
that keeps the structure intact. It tells the both sums apart by indent.
|
|
With the information available from the API JSON, the URL to find the
content archive at can be automatically composed, saving a manual
modification each update.
As the meta data has to be already available for this to happen, the
composed link cannot be part of the original download and extraction
routine. As prepare is part of this step [1][2], recycling some of
makepkg's internal functions in there closely models what would happen
if the file was included in the original source array.
[1]: https://bugs.archlinux.org/task/42433
[2]: https://git.archlinux.org/pacman.git/commit/?id=c034a3322b2a53fce51ffce144e36361892abeac
|
|
|
|
As the protocol already tells, it contains more meta-data than just
version information and should thus be named accordingly.
|
|
It does not only retrieve version information any more but a whole set
of meta-data information, so it should be named accordingly.
|
|
The ever-changing download statistics would change the checksum of the
meta data while the packaging process and results keeps unchanged.
Omitting them yields a checksum that only alters with package changes.
|
|
This paves the way to extracting more information from the JSON that had
to be guessed or managed manually before.
|
|
When trying to extract the tabular information about downloadable files
on the theme page at opendesktop.org, the table apparently containing
the sought information in the loaded webpage lacks any content in the
HTML source code. Examining the load process with Firefox network
analysis gave away an API endpoint from which this data is retrieved via
JavaScript.
Though not much documentation could be found about it, it obviously
provides information about downloadable files in JSON format, which is
much easier to parse than the HTML page intended for presentation to
human eye anyway. Some tinkering found that queries can sensibly be
composed of some of the provided variables. The id is particularily
useful as we already have it in the URL, filtering only on active files
that are actually retrievable helps, too.
|
|
The DLAGENTS modification uses xmllint to extract information from the
HTML page, which is included in the libxml2 package.
|
|
Strings that have nothing to interpret inside them are not be marked
with interpreting double quotes any longer so bash does not even need to
look inside them just to find nothing interesting.
|
|
In the new site, the version has a fixed place in the layout. Fetching
it from there is more secure than fishing it out of the free text
description field.
|
|
|
|
The openDesktop sites were restructured, so all the URLs have to be
adapted accordingly.
|
|
Compatibility to version 3.20 has finally arrived.
|
|
The regular expression had to adapt to a small change in wording.
|
|
The search term now appears multiple times on the new site. Limiting
grep to the first match avoids cluttering the version string with
multiple copies of the same number. Unfortunately, this makes curl emit
an error message because grep will close the pipe as soon as it found
its single match.
|
|
|
|
|
|
|
|
This adapts to a small change in the text.
|
|
|
|
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.
|
|
|
|
Now that the package version can also be readily aware of the compatible
gnome-shell version, the information can be exposed to the user, warning
of possible incompatibilities when updating gnome-shell.
|
|
|
|
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.
|
|
Instead of fixing the file modes after placing them, a cp switch is
available to do both in one go.
|