of main. Why does it have to be int? Well, not returning anything can
result in a random exit code. Add make(1) as caller and the normal
behaviour of just stopping on the first error and this package has
a very low success rate for building e.g. on DragonFly.
- Fixed several serious bugs related to label rendering and printing
that occured when chemtool was built with GTK 2 instead of GTK 1.2
(see ChangeLog for details)
- SVG export now adds a namespace header as required by current builds
of the firefox browser
- SVG export now uses color values instead of color names for better
SVGT compatibility
- The separation between the lines of multiple bonds is configurable
- The keys of the numeric keypad now create two dots instead of a line
for free electron pairs when the Shift key is pressed
- Two new bond types for drawing filled and unfilled p orbital lobes
- chemtool now checks for fig2sxd (sourceforge.net) and offers to export
to OpenOffice Draw format when it is present.
- rpm packages did not install the dutch locale file.
Chnges 1.6.6:
- Fixed bug in molfile preview that caused an immediate crash in 1.6.5
- Made drawing of wiggly bonds work again
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
10.18:
This release contains a fix for the floating point
exception on NetBSD-2.0/alpha.
10.17:
This release corrects the formatting of the man page and
restores the correct alpha-linolenic acid reference
value, which was too low in the last release.
10.16:
This release fixes a segfault that occurs when analyzing
added and subtracted foods that total zero calories.
10.15:
This release completes the changing of all calculations
to substitute user averages for program constants in the
values of calories per gram of carb, fat, and protein,
and of the percentage of total fat that is fatty acids.
This means that personal options in terms of percentages
and ratios will be more precise.
Arka is a program that serves as a graphical interface for the programs from
the GP package.
Furthermore, it has some interesting functions of it's own. The main scope
of the program is the manipulation and visualisation of DNA / RNA / protein
sequences.
This package comes from pkgsrc-wip; created by <hdp at cs.nmsu.edu> with
several changes by me.
A Sequence Cleanup Program. Lucy is a utility that prepares raw DNA
sequence fragments for sequence assembly,possibly using the TIGR
Assembler. The cleanup process includes quality assessment,
confidence reassurance, vector trimming and vector removal. The
primary advantage of Lucy over other similar utilities is that it is a
fully integrated, stand alone program.
New in 10.13:
This release fixes the incorrect "Analyze Meals" screen header that says
"Record Meals". It fixes the function that guesses recipes of packaged foods,
which worked properly but had a variable and a constant of the same value
reversed so that user modifications to increase the precision would fail.
New in 10.12:
The function that guesses the recipes of packaged foods based on the
nutrition and ingredient statements has been rewritten. A much faster
implementation is achieved by quantizing all the values. This algorithm is a
search through all possible recipes because simultaneous equations do not
work for this problem.
New in 10.11:
This release contains a fix for bad Pumpkin Pie values, specifically, null
"carb/prot/fat" values for foods for which the USDA does not supply this
data.
New in 10.10:
This release fixes a bug in the function that allows foods to be added from
food labels. The carb/protein/fat field was not correct because
calories-per-gram fields were not explicitly set.
New in 10.9:
This release contains a fix for wrong calories-per-gram values when the
program starts because it read a float as an integer from the options file.
New in 10.8:
This release contains many small changes, among them an update of the fatty
acid reference values, a removal of the hard-to-obtain "Alaska Native" foods
as food suggestions, and a closer approximation when protein or carbs are
expressed as a percentage of calories.
New in 10.7:
This release changes how personal options are saved to disk so that personal
options will never be lost across program upgrades. Changes have also been
made to how the program upgrades itself on dual-boot systems, and levels of
the Omega-3 reference values have been modified.
New in 10.6:
This release fixes minor bugs related to the "Carb/Prot/Fat" field. Values
for alcoholic beverages have been corrected. Also, an error was fixed that
led to different fat values based on whether the user input changes to the
protein and carb "Daily Values" in percentages or grams. If the two
operations led to the same number of grams of protein and carbs, there should
have been no difference in the fat value.
New in 10.5:
This release adjusts the Omega-3 default reference values, for which there are
no U.S.A. Daily Values, so that EPA and DHA will be higher and alpha-linolenic
acid a little lower.
New in 10.4:
This release contains two minor design changes to the new feature of the last
release, which automatically chooses a meal analysis period. Always choosing
integer days, the new version picks the day closest to the target rather than
the day before; and allows no period shorter than five days, instead of four.
New in 10.3: don't know.
