| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Identified by parsing the NetBSD-i386-5.0.1/2009Q3 pkg_summary files
and Robert Elz.
|
|
|
|
block). Uncomment some commented out LICENSE lines while here.
|
|
- The cdrecord and cdrdao backends are now able to handle ATAPI devices.
This, however, requires fairly recent versions of those tools (see
README).
- Added overburn option for both backends. Currently this must be switched
on manually in the parameters dialog. Maybe in the future we may try to
detect this automatically.
- The cdrdao backend bundle is no longer built and installed by default,
but must be handled separately. This makes things easier for me :-)
- The cdrdao backend now knows the method -availableDrives using cdrdao's
'scanbus' command.
- The 'Burn Tools' panel has now moved to the preferences.
- Split the service 'Burn To CD' into two again: 'Burn To CD' and 'Add To
CD'. This gets us rid of the annoying 'do you want to append or create
new...' message.
- ISO image files may now be opened with a double-click or 'gopen'
(Burn.app registers for suffix .iso).
- The miniwindow for the BurnProgress panel now displays the progress.
- Removed the track types raw-intel and raw-motorola. Noone needs this.
- Add functionality to plug-in audio converters, i.e. bundles that convert
arbitrary audio formats into .wav files.
- Add a converter bundle for MP3 files. This bundle is part of the CVS, but
not of th release package.
Fixed Bugs/Issues:
- Fixed a bug where the 'burnproof' option for cdrecord was was not written
properly to the defaults and thus not used at all.
|
|
|
|
on packages that are affected by the switch from the openssl 0.9.7
branch to the 0.9.8 branch. ok jlam@
|
|
Bump PKGREVISION.
|
|
|
|
"objc" was needed. Thanks to Min Sik Kim for showing me the Right Way to
handle this.
|
|
|
|
Bump revision.
|
|
|
|
ftp://ftp.NetBSD.org/pub/pkgsrc/misc/kristerw/pkgstat/i386-3.0/20060501.1050/broken.html
|
|
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
|
|
of the shlib major bump.
PKGREVISION++ for the dependencies.
|
|
Update some messages/comments.
|
|
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.
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
|
