What's MyBashBurn?
Basically, it is no more than a Terminal User Interface (TUI) frontend based of
the CD burning shell script called BashBurn for GNU/Linux; this originally does
not have the best eye-candy CD-burning UI, nevertheless, MyBashBurn uses dialog
boxes/functions which draws (using ncurses) windows onto the screen. MyBashBurn
dialog boxes offer good functionality, and has very good capabilities of
automatically finding dependencies and auto detecting devices CD/DVD RW. In
short, do not reinvent the wheel - just let MyBashBurn do what you want it to
do.
===> The following configuration options are available for mybashburn-1.0.2_6:
CDRDAO=on: Disk-At-Once Recording
DOCS=on: Build and/or install documentation
DVDTOOLS=on: Frontend to master DVD media
EJECT=on: Ejecting the CD/DVD drive
FLAC=on: FLAC lossless audio codec support
LAME=on: LAME MP3 audio encoder support
MPG123=on: MP3 decoding support via mpg123
NORMALIZE=on: An audio file volume normalizer
SUDO=on: To allow non-privileged users to burn CD's
VORBIS=on: Ogg Vorbis audio codec support
===> Use 'make config' to modify these settings
*/*: Introduction USES=sudo
A new uses 'sudo' has been added to transperently depends of the
proper flavor of sudo 'default' or 'sssd' depending on the default
version set by the user.
If you prefere to use 'sssd' flavor of sudo, add the following
to your make.conf:
DEFAULT_VERSIONS+=sudo=sssd
All sudo consummer ports has benn updated to USES=sudo
Reviewed by: 0mp
Approved by: mat
Sponsored by: Klara, Inc.
Differential Revision: https://reviews.freebsd.org/D52160
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Reset the 99 ports still listed under sylvio@
Sylvio's last commit was 17 months ago, a full 5 months after all of his
ports could have been reset per policy. Given the push to complete
staging (48 ports are still unstaged, something like 70+ have already
been staged by other committers) and given that PRs are automatically
assigned but never addressed, it's better just to reset all the ports and
PRs so that it's clear to others that these ports are free to maintain.
Approved by: portmgr (implicit)
Remove USE_CDRTOOLS from bsd.port.mk
This macros has been useless since cdrtools-cjk port has gone.
This macros also lead to badly handled dependencies assuming that the dependency
on cdrtools was most BUILD and RUN dependency. While most of the time it is
simply a RUN dependency and sometime a build one.
While here:
- Trim some headers
- Convert some ports to optionsng
- Convert some ports to USES= gettext
- update audio/lame to 3.98.4
- use ?= for the portrevision of a master port to make it possible to
change it in a slave port which depends upon lame
- bump portrevisions of ports which depend upon lame
- done via a semi-automated way (manual review and fixup)
- I tried to take care to not bump ports which only depend optionaly on
lame (with a default of no dependency)
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
What's MyBashBurn?
Basically, it is no more than a Terminal User Interface (TUI) frontend based of
the CD burning shell script called BashBurn for GNU/Linux; this originally does
not have the best eye-candy CD-burning UI, nevertheless, MyBashBurn uses dialog
boxes/functions which draws (using ncurses) windows onto the screen. MyBashBurn
dialog boxes offer good functionality, and has very good capabilities of
automatically finding dependencies and auto detecting devices CD/DVD RW. In
short, do not reinvent the wheel - just let MyBashBurn do what you want it to
do.
WWW: http://mybashburn.sf.net
PR: ports/119959
Submitted by: Martin Tournoij <carpetsmoker@xs4all.nl>
Approved by: stas (mentor, implicit)
