| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Waf is also intended to be compiled into a binary for project-local use.
A change in Python breaks these binaries when they are created from a
waf version before 2.0.7. Thus, an explanation on how to recompile and
patch these enables maintainers unable to upgrade to the latest waf
right away to still build their projects.
|
|
This allows for the display of a highlighted code block in a viewer that
understands GitHub Flavored Markdown. For reading in a text editor, it
still is reasonably easy on the eyes while marking the bash commends as
such.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The latter is needed for the semantik [1] package to build, the former a
needed dependency.
Thanks to semantik package maintainer der_fenix [2] for the notice.
[1]: https://aur.archlinux.org/packages/semantik/
[2]: https://aur.archlinux.org/account/der_fenix
|
|
|
|
|
|
|
|
|
|
|
|
This is a minor version change, the API may change significantly.
The 1.8 branch is still maintained, but 1.9 is the new repository master
and advertised on the website, so we try to stay as close to upstream as
possible. Users are advised to upgrade. Severe incompatibilities may
justify the creation of a waf1.8 package.
|
|
|
|
Relying on defaults and directory syntax, the install directives can be
written more concise.
|
|
The library is already installed unpacked into the file system, so there
is no need to keep it duplicated as an archive concatenated to the
binary.
Developers may be used to simply copying the installed binary into their
projects to distribute it. They now need to build a custom binary
manually, which is the recommended way to do anyways, because included
tools can be individually chosen. While it was formerly necessary to
retrieve waf's own wscript to do so, this file is now also distributed,
along with a guideline to ease migration.
|
|
Although waf tools can be installed to the linked wafdir, these files
are then useless for packaging, because at least pacman does not support
files residing below linked directories. Patching the source code to
access the version-independent library directory without symbolic link
detour directs the files to end up in an actual directory again and thus
solves the problem.
With this, the symbolic link is now entirely gone as waf in practice
does not use it any longer.
To divert as little as possible from the upstream source, the new
directory is added as an additional search path. This is especially
important as the existing waf binary may be used as a blueprint
composing a custom waf to include with a project and should thous retain
all original features and avoid unexpected behaviour.
|
|
This not only saves the link, but also directs tools using the internal
Context.waf_dir variable directly to the correct location. While
skipping the link for read access should not improve performance any
noticeable bit, external tools installing to this directory now end up
in the correct place.
|
|
|
|
With a central waflib directory common to all waf versions, packages
that install tools into this directory no longer need to be rebuild
whenever waf is updated.
The changing directory is however kept as a symbolic link for the waf
program itself to use to not mess with patching the code itself which is
probably more difficult to maintain.
|
|
This reverts commit 5b8c86d9b0f785e97bc11df1dd02b6e1a4f086fb "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
|
|
|
|
Optimizing (the first -O) and stripping docstrings (the second -O) saves
space and should improve the speed of waf operation.
|
|
|
|
|
|
|
|
The new version of mksrcinfo released with the recent update to
pkgbuild-introspection adds a header to all .SRCINFO files.
|
|
|