fix: rename ublue-rs to blue-build

src/bin/bb.rs

@@ -1,15 +1,15 @@
+use blue_build::{self, build, template};
 use clap::{Parser, Subcommand};
 use clap_verbosity_flag::{InfoLevel, Verbosity};
 use env_logger::WriteStyle;
 use log::trace;
-use ublue_rs::{self, build, template};
 
 #[cfg(feature = "init")]
-use ublue_rs::init;
+use blue_build::init;
 
 #[derive(Parser, Debug)]
-#[command(name = "Ublue Builder", author, version, about, long_about = None)]
-struct UblueArgs {
+#[command(name = "BlueBuild", author, version, about, long_about = None)]
+struct BlueBuildArgs {
     #[command(subcommand)]
     command: CommandArgs,
 
@@ -35,7 +35,7 @@ enum CommandArgs {
 }
 
 fn main() {
-    let args = UblueArgs::parse();
+    let args = BlueBuildArgs::parse();
 
     env_logger::builder()
         .filter_level(args.verbosity.log_level_filter())

src/lib.rs

@@ -1,12 +1,4 @@
-//! The root library for ublue-rs.
-//!
-//! This module consists of the args for the cli as well as the
-//! initial entrypoint for setting up tera to properly template
-//! the Containerfile. There is support for legacy starting point
-//! recipes using the feature flag 'legacy' and support for the newest
-//! starting point setup using the 'modules' feature flag. You will not want
-//! to use both features at the same time. For now the 'legacy' feature
-//! is the default feature until modules works 1-1 with ublue starting point.
+//! The root library for blue-build.
 
 #[cfg(feature = "init")]
 pub mod init;