Collection. The list is a five-field CSV file.
Free list of UK postcodes
The list is formatted as plain text, with each record on a separate
line. Each record consists of five fields, each field being separated
by a comma. You should be able to import this data into most
applications that support "comma separated variables". The five
fields are:
1. First part of the UK postcode (area code)
2. x-coordinate (metres)
3. y-coordinate (metres)
4. Latitude
5. Longitude
* Updated translations:
Adam Weinberger (en_CA)
ahmad riza h nst (id)
Alessio Dessì (it)
Jordi Mallach (ca)
Jyotsna Shrestha (ne)
* Fix for bug #171231 GOK sometimes hung when UI grabbing Yelp.
* Fix for bug #170347 User is stuck when using the repeat key on a drop-down menu
* Fix for bug #169761 Tidying up some code.
* Fix for bug #160726 to allow gok to pass make distcheck.
2005-03-07 Irene Ryan <irene.ryan@sun.com>
* help/gok/C/gok.xml: updated date, manual version,
and s/w version number
* help/gok/C/gok-C.omf: updated version and date details
by me.
C language function library for predicting the spread rate, intensity,
flame length, and scorch height of free-burning surface fires. It is
derived directly from the BEHAVE fire behavior algorithms for
predicting fire spread in two dimensions, but is optimized for highly
iterative applications such as cell- or wave- based fire growth
simulation.
and koffice build.
And do in meta-pkgs/kde3/kde3.mk as suggested by maintainer, markd.
It helps with builds on Linux for kdegraphics3, libkipi, gwenview,
kdelibs3, kdebase3, arts, and many other KDE-based packages on Linux.
(It was not needed for kile, but will be used.)
Thank you, Torsten Harenberg for testing many packages such as
kdenetwork, kdegames, kdepim, kdemultimedia.
I still don't know what the correct fix is for PR #25402.
caches variable definitions that were computed by make. These variables
are specified by listing them in MAKE_VARS, e.g.,
.if !defined(FOO)
FOO!= very_time_consuming_command
.endif
MAKE_VARS+= FOO
bsd.pkg.mk will include only the one generated during the most recent
phase. A particular phase's makevars.mk file consists of variable
definitions that are a superset of all of the ones produced in previous
phases of the build.
The caching is useful because bsd.pkg.mk invokes make recursively,
which in the example above has the potential to run the very time-consuming
command each time unless we cause FOO to be defined for the sub-make
processes. We don't cache via MAKE_FLAGS because MAKE_FLAGS isn't
consistently applied to every invocation of make, and also because
MAKE_FLAGS can overflow the maximum length of a make variable very
quickly if we add many values to it.
One important and desirable property of variables cached via MAKE_VARS
is that they only apply to the current package, and not to any
dependencies whose builds may have been triggered by the current
package.
The makevars.mk files are generated by new targets fetch-vars,
extract-vars, patch-vars, etc., and these targets are built during
the corresponding real-* target to ensure that they are being invoked
with PKG_PHASE set to the proper value.
Also, remove the variables cache file that bsd.wrapper.mk was generating
since the new makevars.mk files provide the same functionality at a
higher level. Change all WRAPPER_VARS definitions that were used by
the old wrapper-phase cache file into MAKE_VARS definitions.
package because PKG_OPTION.<pkg> could contain negative options, which
are never part of PKG_OPTIONS. Instead, use the show-var target to
display the value. We cache it in WRAPPER_VARS and in MAKE_FLAGS to
prevent reinvoking the show-var target recursively.
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
some features added (libcdparanoia cloned, CD audio), some fixes
not quite mature, but we have to update because the API changed
(in the iso9660 area), and other pkgs (vcdimager, vlc) depend on it
Changes since 2.7.4:
- fixed HTML export (not all text format options were processed,
weekday color column was not implemented) and improved layout
- fixed timezone format in XMLTV output (DTD 0.5, local timezone only)
Thanks to Laurent Garnier for reporting the bug.
- XML export: format can now be selected via command line options
- added command line option -outfile <path>
- Improved network/channel identification by VPS/PDC during
interaction with TV applications (e.g. TV5 was not identified)
- Added support for reading channel table of K!TV 2.3
Thanks to Quenotte for providing a patch.
- Windows only: fixed !wintv! keyword handling in scripts bound
to reminder events (this was already supposed to be in 2.7.4 but
lost somehow)
- Windows only bugfix: "Record this show" did not appear in context
menu when connected to K!TV
- bugfix: missing error-check in time conversion lead to inconsistant
start/stop times around daylight saving time switch (which lead to
error "database corrupt" during reload)
RubyGems is a way to package Ruby libraries/applications for
distribution, its a distribution manager, its a package manager.
RubyGems brings to the world of Ruby a very valuable capability--the
ability to manage concurrent versions of libraries and dependencies
between those libraries. This last aspect of RubyGems is one of the
most important to the end user, because its value is continuous as you
use and program Ruby, but to understand its impact an explanation of
how Ruby manages libraries is in order.
