bigbang (development version)
Tests
- The tests pass again when coverage is measured with covr 4.0.0. Generated meta-packages embed bigbang’s archive reader as deparsed source. Under covr that source carried the counters covr adds, and with covr 4.0.0 it no longer parsed back to the same functions (r-lib/covr#776). bigbang now removes coverage counters before it embeds the reader, and checks that the embedded code parses back to the same functions.
bigbang 0.6.1
CRAN release: 2026-11-17
Bug fixes
-
<meta>_deps(plan = TRUE)warns, with classbigbang_warning_install_library, when the installers would not be able to use the installation library:- it does not exist and cannot be created, because its first existing ancestor is not a directory with write and search permission, or is a dangling or looping symbolic link;
- it exists but is not writable, and the plan has something to install.
libthat is an existing regular file remains an error, as in the installers. - When a re-exported symbol is unavailable because its component is not installed, the error says so directly instead of nesting “component is not installed” inside an installed-version label, in English and Spanish.
- The warning
install_local_pkg()gives for an archive inpkg_dirthat it cannot read now has the classbigbang_warning_archive_inventory. An archive that cannot even be opened gives that single warning, with the reason, instead of an extra warning from R. Each archive is reported once per call, even when a package is requested by name andpkg_diris searched more than once; it used to be reported up to three times. - The warning about archive names that only pass with
bigbang.archive.portable_names = FALSElists the first three names and how many more there are. - On Windows, the excerpts of
R CMD INSTALLerrors thatinstall_local_pkg()and generated installers show no longer end each line with a stray carriage return. - When a component is given as a source directory,
diagnose_dependencies(),install_local_pkg()andcreate_metapackage()build it once per call and remove their temporary build directories when they finish, also after an error. These directories used to stay in the session’s temporary directory.
Tests
- The tests cover more of the archive reader’s rejections (PAX, CRC, ZIP and tar layout, limits) and of the installation diagnostics.
- Under CRAN settings, the tests run fast unit checks and a smoke test of each area, in about a quarter of the previous time. The integration tests, which generate, build and install meta-packages, run with
NOT_CRAN=true, as in the project’s CI.
bigbang 0.6.0
CRAN release: 2026-10-23
Security
-
bigbang now reads tar and ZIP archives with its own validating reader, and no longer calls
utils::untar()orutils::unzip(). On R 4.1 to 4.5, a component archive containing a symbolic link, followed by an entry written through that link, could write outside the temporary extraction directory before bigbang rejected the archive, even withdry_run = TRUE. R 4.6.0 blocks this insideuntar(), but earlier releases do not.The new reader:
- creates only regular files and directories inside the destination;
- treats Windows junctions and symbolic links as links, so it never extracts into them and its cleanup never deletes through them;
- rejects links, devices, other special entries, and malformed, overlapping or trailing archive data;
- by default rejects names that Windows cannot create, such as
aux.Ror a name containing:or?, names ending in a dot or a space, and names that differ only in case. If every recipient uses Linux or macOS,options(bigbang.archive.portable_names = FALSE)accepts them wherever the file system can store them, which is never on Windows, and warns that the package will not install there. Links, absolute paths,.., names made only of dots and spaces, control characters and invalid UTF-8 are always rejected; - verifies CRC-32 and sizes through zlib;
- stops at configurable limits:
options(bigbang.archive.max_entries, bigbang.archive.max_total_bytes, bigbang.archive.max_metadata_bytes, bigbang.archive.max_path_bytes)(see?scan_bigbang_artifact).
Generation,
diagnose_dependencies(),install_local_pkg(),scan_bigbang_artifact(), and the installers of generated meta-packages all use the same reader.scan_bigbang_artifact()reports an archive with links as vulnerable, and a damaged one as an archive error, instead of failing.
Dependencies
- bigbang now requires R >= 4.1.0. Its own code needs nothing newer than R 3.6.0. The imported glue, however, has required R 4.1 since glue 1.8.1, so installing on an older R already failed unless an older glue was installed by hand. CI now checks R 4.1. Generated meta-packages keep their
R (>= 3.5.0)floor, which has been verified on R 3.5.3.
New features
-
<meta>_deps(plan = TRUE)returns a read-only plan of what<meta>_install()will do. It reports, for each component, the archive and installed versions, the library, the action and the reason, and, for each external dependency, its version constraint and whether it is satisfied. The plan uses the installer’s ownupgradedefault,onlyclosure, and rules for libraries and version constraints. It loads no namespaces and installs nothing.<meta>_deps(only = ...)also lists the dependencies of that closure without a plan. Called with no arguments,<meta>_deps()returns what it did before. -
create_metapackage(governance = TRUE)adds aCONTRIBUTING.md, a code of conduct adapted from the Contributor Covenant 2.1, and a package-inclusion issue template to the generated meta-package. Updates track these files, and the built package excludes them. The default remainsgovernance = FALSE.
Bug fixes
-
Name collisions. A meta-package whose name matches one of its components, or another local package the installer can see, is rejected before anything is written, ignoring case. So are two components whose names differ only in case. The generated installer also rejects an archive whose
Package:field changed after generation. -
Failure messages. When
R CMD INSTALLfails,install_local_pkg()and generated installers now report the last real error, together with the lines around it, and give the path to the full log. Compiler errors are included, and logs that are not valid UTF-8 are read safely. -
External dependencies. Version constraints on external dependencies are checked for each component. With
cran_deps = "install", an unsatisfied dependency is updated from the explicitrepos. Nothing uses the network without an explicit, non-emptyrepos. -
Source-only repositories. On Windows and macOS,
cran_deps = "install"installed nothing from a repository that only has source packages, such as an internal repository, and the reason was discarded. If the default attempt leaves a dependency unsatisfied,install_local_pkg()and generated installers now retry withtype = "source", so binaries are still preferred where they exist. When both attempts fail, the result says why. - Result categories. Every component ends in exactly one result category. Dependents of a failed or skipped component are skipped without being built, and a shared dependency is installed only once.
-
Installed components. Without
lib, a component installed in any library on.libPaths()counts as installed. With an explicitlib, only that library counts. - Translations. Printed results, installation results and every message emitted by generated meta-packages are translated into Spanish. Tests now fail on any untranslated message, and the English output is unchanged.
-
Smaller fixes.
- A meta-package generated with
document = FALSEno longer declares aRoxygenNotefor a roxygen run that never happened. - Replacing a file through a Windows reparse point no longer warns.
- An invalid
lib, such as an empty string,NAor several paths, gives the same classed error ininstall_local_pkg(),<meta>_deps(plan = TRUE)and generated installers. When the installers cannot create the library, they fail with that error too, with nodir.create()warning before it. - 46 obsolete entries were removed from the Spanish catalog.
- The test suite no longer depends on what is installed in the user library.
- A meta-package generated with
Performance
- Archives are listed once per call: listing ten 1 MB archives went from 64 to 19 ms.
-
install_local_pkg()no longer rebuilds shared dependencies.
Documentation
- The README citation section points to
citation("bigbang")and explains the CRAN and Zenodo DOIs. It no longer pastes a BibTeX entry, which had been left at version 0.3.0. - The README now explains that recipients keep a newer installed version by default (
install_upgrade = "newer"), and thatinstall_upgrade = "always"makes every installation match the archives. - The vignettes use
<meta>_reexport_verification()only withreexport = TRUE, and quote the path given toR CMD build. - Smaller fixes:
- the README describes the self-contained meta-package, r-universe binaries and CI accurately;
- the Spanish README gains the sections it lacked;
-
CONTRIBUTING.mddocuments the test and lint commands.
bigbang 0.5.1
CRAN release: 2026-10-06
Bug fixes
- Each component archive is listed and extracted once per generation, diagnostic, or local installation call, and re-export source evidence asks R for the text of the parse tokens it needs only. Generating a re-export meta-package for 11 components is about four times faster, with the same plans and diagnostics.
- Attaching the components of a re-export meta-package no longer evaluates its re-export bindings, and
<meta>_conflicts()and<meta>_deps()do not evaluate them either. R’s own load test at the end ofR CMD INSTALLcan still evaluate them. - Re-export mode no longer prints R’s “The following objects are masked…” messages for deliberately re-exported symbols; use
<meta>_conflicts()to inspect those intentional conflicts.
Documentation
-
install_local_pkg()has an example that installs the bundled example archive into a temporary library.
bigbang 0.5.0
CRAN release: 2026-10-02
Breaking changes
-
update = TRUErefuses a planned generated path that already exists outside the manifest, including generated documentation files that were previously regenerated over it. Remove or rename that file to let the update write it. -
bigbang_error_missing_projectnow inherits frombigbang_error_missing_manifestwhile identifying a missing project more precisely. -
dry_runnow reports a read-only reconciliation plan for sibling journals and the project lock; uncertain owners requirerecover = TRUE. - A failure while promoting generated documentation now aborts the update and rolls the project back through its journal. Only failures in the staging generation remain warnings.
-
create_metapackage()now acceptsreexport_preferandreexport_exclude. Every collision requires one of them because static analysis cannot prove object identity, and diagnostics classify the selected resolution. - Generated metapackages now reserve
.component_reexport_specs,.reexport_state,.reexport_library_paths,.set_reexport_library,.reexport_component_value,.reexport_installed_version,.reexport_loaded_version,.reexport_version_text,.make_reexport_binding,.install_reexport_bindings,.reexport_verify,.reexport_verify_subprocess,.meta_package_version,<meta>_reexport_verification, and the generated installer, lifecycle, dependency, diagnostic, and translation helpers. Migrate colliding component exports withreexport_exclude = "...". Version 0.4.0 already rejected these collisions; 0.5.0 adds explicit choose-or-exclude handling and diagnostics. - Re-exporting R syntax names such as
if,[, or arithmetic and comparison operators now requiresreexport_exclude. Version 0.4.0 did not reserve those names, so a component export could shadow syntax in generated code and in the attached session. Migrate by excluding the syntax names; the generated metapackage retains R’s syntax and its installer remains usable.
New features
- Interrupted updates now use a durable journal, resumable tombstones, and an exclusive project lock; recovery preserves unverified user bytes and supports read-only planning.
- Re-export diagnostics follow same-package helpers and classify calculated destinations and foreign namespace indirection conservatively.
- Installed-owner verification runs in a clean R subprocess with the destination library first, and the conflicts accessor keeps verification outside symbol names.
- Update recovery accepts the
recoverargument and reportsrecovered,recovery,reexports, andreexport_excludedin its result. The generated<meta>_reexport_verification()accessor returns installed-owner checks. - Dependency scanning now includes
.S,.s, and.qsources; detected dependencies can therefore differ from earlier releases. - Updates can now add planned files that are absent from both the manifest and the project, including new, re-added, or version-bumped components and workflow vignettes; existing untracked paths are refused as user content.
Bug fixes
- Generated metapackages:
<meta>_detach()detaches components from the top of the search path down, so families linked throughDependsdetach completely;library(<meta>)reports components that cannot be attached, such as one whoseDependsare missing or whose namespace was loaded from another library, instead of failing; installer messages respectverbose = FALSE;<meta>_conflicts()compares namespace exports, so internal objects such as.Dependsare no longer reported as conflicts. - A warning about an archive whose file name and
DESCRIPTIONversion differ is now given once per archive and installation call. - Fixed a 0.4.0 defect where an installed older component that no longer exported a re-exported symbol made
R CMD INSTALLfail while loading the metapackage. Re-export bindings now always evaluate safely and provide an actionable<meta>_install()placeholder error when called. - Components skipped because a local dependency was skipped are now reported as skipped with the chained reason, and the skipped summary is shown even when another component fails.
- Discarded-journal cleanup now sets aside unreadable content, revalidates paths and MD5 values immediately before deletion, checks every discard unlink, and moves unreadable armed journals aside during recovery. Verification now reports unavailable checks, preserves its accessor class, uses the runtime library when no destination library exists, qualifies subprocess helpers, and reports namespace unload failures with their importing package and restart guidance. Windows liveness never probes a process with a terminating signal.
- Update locks now decide discarded entries from the recorded owner before the claimant, preserve live owners byte-for-byte, revalidate ownership before journal mutations, and process discarded entries until no progress remains. Zombie and permission-sensitive liveness is conservative, symlink locks have a working recovery path, and lock-creation errors identify the parent failure. Unix systems without
/procnow record a locale-independentps lstarttoken, and the retry guard counts only consecutive no-progress attempts. - Armed journal recovery now rejects mismatched
state.rdsandmarker.rdsowners instead of rolling back a live update. Clean re-export verification now follows the runtime library order and distinguishes installation, export, and foreign-library failures. - Fixed the 0.4.0 regression where generated metapackage machinery could be hidden by an export with the same name.
- Journal inventory and discard cleanup no longer follow directory symlinks; linked entries and their descendants are set aside byte-for-byte.
- Installation verification no longer reuses a namespace loaded from another library and never reports identity when a clean verification is unavailable.
- Generated re-export calls now qualify base, utils, tools, and methods helpers; source validation and generated diagnostics remain safe when components export those names.
- Re-export source evidence reuses per-file parse indexes, and update recovery preserves staged files and unknown external deletions conservatively.
bigbang 0.4.0
CRAN release: 2026-08-19
New features
The project lifecycle is now documented as stable: its public API has remained stable since 0.1.0 and is protected by an extensive regression suite and repeated independent adversarial reviews.
create_metapackage(reexport = TRUE)now exposes explicit component exports through lazy, read-only active bindings without making components installation dependencies. Generated metapackages can load offline before their components are installed, and the bindings resolve after a later installation.Runtime re-exports now exclude S4 class and method directives, reserve every generated helper symbol, preserve untracked
reexports.Randreexports.Rdfiles during updates, avoid loading components for startup reporting, and support installation into a new library directory.Component inputs now accept a bare package name when exactly one archive in the supplied directories declares that
Packageidentity. Ambiguous versions or sources are rejected with the full candidate list.
Documentation
- The acknowledgments now use Richard Detomasi’s current contact and profile, retain the precise credit for the initial metapackage-builder suggestion, and identify
pegeler/metapackageas a related online declarative metapackage.
Bug fixes
Bare package-name discovery now warns when an unreadable archive is excluded and suppresses uncontrolled tar diagnostics while retaining readable matches.
Runtime re-exports quote non-syntactic names in generated NAMESPACE files, so legal exports containing spaces or Unicode characters produce installable metapackages and working active bindings.
removed_filesnow includes partial documentation outputs that a generation call created and cleaned up after roxygen failed. Dry-run plans continue to report only removals that are knowable before generation starts.
bigbang 0.3.0
This release makes the package accept component packages as an organisation actually keeps them, instead of requiring one directory, one archive extension, and a version in every filename. Package identity now comes from each archive’s DESCRIPTION rather than its filename, generation can report a plan without writing anything, and the checks that concern project tidiness can be relaxed individually. The checks that protect whoever installs the generated meta-package cannot: they remain hard errors during generation.
It also supersedes 0.2.0, which was prepared and verified but never submitted. Everything listed under 0.2.0 below reaches CRAN for the first time here, so a user updating from 0.1.0 should read both sections.
Breaking changes
-
reexportis deprecated and ignored. Generated metapackages attach installed components, so their exports remain available directly or through each component namespace, but they are not copied into the metapackage namespace. Re-exporting would require declaring components as installation-time dependencies, which conflicts with explicit offline component installation; the option did not produce a valid package in the published 0.1.0 release.
Component archives can come from anywhere
- Any element of
packagesthat is an existing file is used as a path, so components can come from several directories in one call and mix.tar.gz,.tarand.zip. Stems still work, resolved againstpkg_dir, which now accepts more than one directory. -
Package identity and version come from each archive’s
DESCRIPTION, not from its filename, so a filename without a version is valid. A filename that disagrees with theDESCRIPTIONproduces a warning and theDESCRIPTIONwins. - A component may be a source directory with a
DESCRIPTIONat its root, built for you with the optionalpkgbuildpackage. It requiresinclude_archives = TRUE, because the archive built for it lives in a temporary directory that does not outlive the call. -
packagesmay be the path to a manifest: one component per line,#for comments. Relative paths resolve against the manifest’s own directory, absolute and~paths are used as given, and bare filenames are also looked up inpkg_dir, so the list can live under version control while the archives do not. A missing entry reports every directory that was searched.
Seeing what a call would do before it does it
-
create_metapackage(dry_run = TRUE)resolves and validates everything and returns the plan — components, installation order, files that would be written, and every validation finding — without creatingdest_diror writing anything.
Strictness you choose, within limits you do not
-
create_metapackage()gains a finaltolerateargument taking a closed list of named relaxations:"filename_mismatch"silences the filename-versus-DESCRIPTIONwarning, and"unincluded_local_dep"turns the error for a local dependency available in the supplied sources but omitted frompackagesinto a warning. That second relaxation means the dependency does not travel, so the recipient has to supply it. Unknown names are errors, not silent no-ops. - Generation results include a
toleratedtable naming every applied relaxation, the component it affected, and why. -
on_component_error = "skip"generates from the components that are valid instead of aborting, and reports the ones it left out. The exclusion is transitive: a component that depends on an excluded one is excluded too, and the chain is reported. When the omitted archive can be read, its declaredPackagedrives the exclusion; when it cannot, the filename fallback is reported explicitly. Excluding every component is an error. - The documentation now separates the two classes of check: validations that protect whoever installs the generated meta-package cannot be disabled by any value of
tolerate, and there is no switch that turns validation off as a whole. It also states explicitly that bigbang does not runR CMD checkon component packages, so a component with check warnings or notes can be included.
Regenerating in place
-
create_metapackage(update = TRUE)regenerates an existing project, which relaxes the rule that a destination must be new or empty. Generation records a manifest of the files it wrote together with their content hashes;updaterewrites only those, and refuses to run if the manifest is missing or if a generated file was modified or removed by hand. - Files bigbang did not write are never touched.
updaterefuses when a generated file, or any parent directory on the way to it, is a symbolic link, and it replaces generated files and shipped archives atomically, so a regeneration cannot write outside the project tree. - When components or options are dropped,
updatereconciles: generated files and shipped component archives that the new plan no longer includes are removed transactionally, so the regenerated meta-package cannot end up importing from a component it no longer declares. Before changing an existing project, bigbang backs up all generated files and its manifest. If generation or reconciliation fails, that state is restored and the update remains retryable. Dry runs and completed updates report the affected paths inremoved_files; removing a component may remove the last available copy of its shipped archive.
Generated installers
-
<meta>_install(only = ...)installs a subset; local dependencies of the selection are added automatically, and an unknown component name is an error. -
<meta>_install(lib = ...)chooses the library in which components must be installed and verified. Non-local dependencies may already be available in that library or anywhere on.libPaths(); they no longer need to be duplicated into the component destination. -
create_metapackage(install_upgrade = ...)fixes the default upgrade policy of the installer that gets emitted, so the person generating decides whether recipients stay pinned to the versions being shipped or keep anything newer they already have. The default is unchanged. - The installer accepts a vector of archive directories when the archives are not shipped, and archives that do travel inside a generated meta-package contain no path from the machine that produced them.
- Real generation results now include the same topological
orderfield as dry-run plans. The plannedfilesfield remains specific to dry runs. - When installing a source component fails,
install_local_pkg()and generated installers now report the error lines of the installation subprocess itself – for example, which dependency it could not find – instead of only a generic verification failure.
Bug fixes
- A failed documentation run during
update = TRUEno longer deletes or leaves partially overwritten an untracked Rd file whose name is reserved for generated documentation. Such files are backed up before roxygen runs and restored without being adopted into the generation manifest. - Migrating a development-era schema 1 generation manifest now adopts only the shipped component archives that belong to the current plan. An unrelated archive placed by the user under
inst/archives/remains untracked and is never removed by a later update. - Documentation outputs can be disabled and re-enabled across updates. If roxygen fails during an update, previously tracked Rd files are restored and retained in the manifest, while partial newly generated Rd files are removed, so a later documentation update remains possible.
- Update manifests are now built from the explicit generation plan instead of scanning the project tree. Repeated updates no longer absorb and later delete user files, including files under
.git/. - With
on_component_error = "skip", a failed update input no longer authorizes deletion of a previously shipped component archive. If the old component cannot be identified safely, archive reconciliation is deferred until a clean update. - Updates now reject a generated project whose root entry is itself a symbolic link, in addition to links below the project root.
- Successful source-install transcripts now honor
verbose = FALSEin bothinstall_local_pkg()and generated installers; failure details still retain the child process’sERRORlines. -
install_local_pkg(lib = ...)and generated installers now distinguish the component destination from the dependency search path: a component present only elsewhere is installed intolib, while a non-local dependency already available elsewhere on.libPaths()is reused. This also works under the dependency isolation used byR CMD checkon Windows. - A component archive with an upper-case extension —
PKG_1.0.TAR.GZ, as they often arrive from Windows — was shipped under its original name while the generated installer looked for the normalised one. The component was never installed on a case-sensitive filesystem, with no error anywhere. Archives are now copied under canonical names, and names that collide only by case are rejected. - An unreadable archive unrelated to the requested components, left in a supplied source directory, aborted generation. Such archives are now excluded from the inventory with a warning, and there is a specific diagnostic when a declared dependency appears to match one.
- Installing a package that is already present no longer requires reading its archive when
upgrade = "never"; under the default policy only the archive’sDESCRIPTIONis read before deciding whether the archive is needed at all. An unreadable archive is reported as unchanged when the installed package can be kept, instead of failing the call. - A failed resolution of several components kept only a placeholder name in the installation result; the requested names are retained.
- Installation messages name both the package declared by the
DESCRIPTIONand the archive it came from when the two differ, instead of reporting the filename as though it were the package. - Reading an archive’s version for the installation shortcut now rejects extracted symbolic links before reading metadata, matching the guarantees of the full archive validation path.
- Rolling back a generation that failed after the project tree existed is now exercised, including destinations reached through a symbolic link and a removal that does not succeed.
Documentation
- The installation help explains that under
upgrade = "never"the component is identified from its filename, because the archive is deliberately not read; use the default policy when the declaredPackagehas to be checked against what is installed. - The README, in both languages, documents where components can come from and every generation option. It previously described the input model the package had before this release.
bigbang 0.2.0
Prepared and verified but never submitted: CRAN submissions were closed between 2026-08-05 and 2026-08-19. These changes are released as part of 0.3.0.
Breaking changes
- The deprecated Spanish aliases
crear_meta_paquete_local(),diagnosticar_dependencias()andinstall_loc_pkg_w_dep()were removed. They existed to ease a rename inside the organisation the package grew in, while it was still unpublished. Usecreate_metapackage(),diagnose_dependencies()andinstall_local_pkg(). - In a generated meta-package built with
include_archives = FALSE,<meta>_install()requirespkg_dir. In 0.1.0 that argument defaulted to the absolute archive path of the machine where the meta-package had been generated, which exists nowhere else. With the new default,include_archives = TRUE, the argument is optional again because the archives travel inside the package. - Components that the installation policy left untouched are reported in a new
unchangedelement of the installation result instead of appearing ininstalledlabelled “Already installed”. Reporting a package as installed when nothing was installed was misleading. - Non-local dependencies are installed with
dependencies = NAinstead ofTRUE, so theirSuggestsare no longer installed. Everything a component needs in order to run is still installed; what is no longer pulled in is the tooling those dependencies use for their own examples, tests and vignettes. - Source-code guesses from
detect_implicit_dependencies()are now diagnostic only. Dependencies declared by a component, or supplied explicitly throughadditional_deps/force_deps, remain binding; guessed packages must be opted in explicitly. This prevents comments and common function names from making a distributed meta-package depend on unrelated packages. - Generation now rejects a local dependency constraint that the included archive cannot satisfy, and rejects a local archive that is present in
pkg_dirbut was not included inpackages. Component R version requirements are propagated to the generated DESCRIPTION for enforcement on the recipient’s R version. - The arguments added in this release come last in every signature, so a positional call written against 0.1.0 keeps binding to the same parameters. Positional calls are still a fragile way to call these functions: name the arguments.
Generated meta-packages are self-contained
-
create_metapackage()gainedinclude_archives,TRUEby default, which copies the component archives intoinst/archives/of the generated meta-package. Its installer then defaultspkg_dirtosystem.file("archives", package = "<meta>"), resolved when the installer is called, so the meta-package is the only artifact that has to be distributed and its components install with no arguments, with no path agreed on beforehand. Network access remains necessary only for components that depend on a package coming from a repository. Passinclude_archives = FALSEto keep the archives in a shared location the recipient can reach. - The build ignore rules of a generated meta-package exempt
inst/archives/, so shipped components reach the tarball while every other archive anywhere in the tree is still excluded.
New features
- Generated meta-packages provide an optional
clitwo-column startup message that falls back to the ASCII banner whencliis absent, a<meta>.quietoption,<meta>_conflicts()for masking conflicts, explicit reinstall and upgrade policies (force, andupgrade = "newer" | "always" | "never"), and an optional ordered workflow vignette through theworkflowargument. - Generated metadata records the component list in
Config/bigbang/packages, and the generated package tests that the list agrees with what it exports.
Bug fixes
- Rollback of a failed generation works when a component of the destination path is a symbolic link. The project path was normalised before the directory existed and therefore left unresolved, while the path it was compared against was normalised after creation and resolved, so the two never matched and the rollback declined silently. That is the situation on macOS, where
tempdir()sits under/var, itself a link to/private/var. Both sides are now normalised at the same moment. - An archive whose root directory is accompanied by an AppleDouble
._<dir>member is accepted. Archiving a package directory on macOS with extended attributes emits one, and R installs such an archive, so rejecting it rejected a working package. -
diagnose_dependencies()extracts through the same guarded path as generation. A component carrying a symbolic link made the scanner read a file outside the archive and return its contents in the result. - Generation no longer changes the process working directory; every scaffold writer receives an explicit absolute path.
- Fixed generation with relative
dest_dirandpkg_dirpaths, and roll back incomplete project trees created by a failed invocation. -
create_metapackage()validatesnamebefore writing anything: against the R package name grammar, and against the names R itself ships. A name carrying a path separator or a parent reference previously placed the generated tree outsidedest_dirand still reported success. - Non-local dependencies are installed with
dependencies = NA, which covers Depends, Imports and LinkingTo, instead ofTRUE, which also covered Suggests. Asking for one small dependency used to pull development tooling and its whole tree into the library. - Restored the caller’s attached packages and loaded namespaces after automatic documentation, and report documentation success accurately.
- Fixed eleven Spanish runtime messages whose catalog keys had leading or trailing whitespace.
- Generated helper examples use the requested meta-package name instead of an internal historical name.
- Paths returned in results use forward slashes on every platform, like the rest of the package. On Windows
result$pathcame back in the platform convention and therefore did not compare equal to a path the caller had built withfile.path(). The containment checks normalise both sides the same way, so a destination that does not exist yet cannot be compared against one that does in a different convention. - When a component is skipped because a non-local dependency is missing, the warning names the call that resolves it and the attachment step no longer follows it with a vaguer hint suggesting a bare re-run, which would have skipped the component again for the same reason.
- Component archive
PackageandVersionfields are validated against their filenames, duplicate component versions and archive basenames are rejected while generating, and generated installers verify the declared version. - Already-installed messages now report the installed version rather than the version named by the archive.
- Component names matching standard R package paths no longer generate
.Rbuildignorerules that could exclude the generated package’s own files or shipped archives. - Already-installed messages show both the installed and archive versions, and explicitly flag when the installed version is newer. The
unchangedelement of an installation result now carries the same two versions instead of the label “Already installed”, which is untrue when the installed package only shares a component’s name; the result is the only thing a calling script can inspect. - Archive inspection now validates extraction status, member paths, symbolic links, and the single package root before accepting an archive. Nested
tests/DESCRIPTIONfiles are allowed, while a missing root DESCRIPTION is reported clearly. - Malformed component R files produce a warning naming the component archive and the path inside it, while generation continues, so a possible encoding issue is diagnosable without turning generation into an unconditional rejection. The warning no longer names the extraction directory, a temporary that no longer exists by the time the warning is read.
- Rollback removes an empty destination directory created by the failed call, and
safe_unlink()uses temporary-directory containment rather than a broad basename heuristic. - The source-code patterns require a namespace qualifier or a call for every package they guess at, so ordinary S4 code is no longer reported as needing
Matrix, and an identifier beginning withst_no longer suggestssf.
Documentation
The maintainer’s given name is spelled Sebastián, and the author entry now carries an ORCID identifier.
Documented that distributing the component archives inside a meta-package is a redistribution, so their licenses have to allow it, and that a component still installs only where its format can.
Documented related meta-package projects and design precedents.
Added the r-universe version badge and the one-line install from the universe binaries.
bigbang 0.1.0
CRAN release: 2026-08-08
First release on CRAN, accepted on 2026-08-08.
bigbang — create custom R metapackages from local packages
Data-safety architecture
- Removed all generated startup installation and cwd-relative cleanup. Generated
.onLoad()hooks are side-effect free; component installation is explicit via<meta>_install(). - Added destructive regression tests in disposable directories, including real source installation, attachment, data-only components, names beginning with
tmp, and content hashes for decoy directories. - Added
scan_bigbang_artifact()to identify the historical V1/V2/V3/V7 signatures in source trees, archives, and installed packages without loading them. - Generated projects must use a new or empty destination, preventing unsafe in-place regeneration of unclassified historical sources.
Installation and portability
- Component archives are installed once in topological dependency order; cycles raise a typed
bigbang_error_cyclecondition. - Added explicit offline dependency policies (
skip,error,install) and content-based distinction between source ZIPs and Windows binary ZIPs. - All generated text is written as UTF-8, R literals and paths are emitted safely, and CI covers Linux, Windows, and macOS configurations.
API, language, and documentation
- Added the English snake_case API:
create_metapackage(),install_local_pkg(), anddiagnose_dependencies(). Spanish aliases remain available as deprecated transition wrappers. - Added typed results and conditions with print methods.
- English is the source language. Spanish runtime translations are supplied through gettext for both
bigbangand generated metapackages. - Added English and Spanish guides, release documentation, and a pkgdown configuration.
