autotrace 0.1.9 → 0.1.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7272a2b850e301d77b91293d841e67f51ae38f37ca7fe4ba5f1fff695a536f73
-  data.tar.gz: 0afb61a635355976b6f6ed9277da2f427e9f67b8e73cb572b7b4a3a266e2cd92
+  metadata.gz: 2e0b6a0eaa8fa8c033ad3873ffba677970de16dfdc5904f2d276204ce6428476
+  data.tar.gz: a713ed754342aa28a31ceb5a29e5bf5c51cd914fa69332d3c780856443f97e46
 SHA512:
-  metadata.gz: 3eb0e1ac38c154a616b3abf32e422cc645c4c6510c3aa15936cab379eb7b1517fb1ef991f1a213388a555f11c5748e2dc6834507820e2dcba50d115f4f19ebfb
-  data.tar.gz: f7a219dbc8d55b7adf142901cc2c3ead7b18155b9484a124250248b8a94c94bc37aeb98ac8557a93fff82d71d1bf6b8de4ed62cdbc6a2a155d386b26131f24e0
+  metadata.gz: 16a37032bd30960ada05ccae70e030445aa90f775e518c3f4e872fb5290c465f1f57f9ee8f5e2d5aec7fbbf42857aabc32ff2f9511b9cef34567d409fe5cd1b9
+  data.tar.gz: 3e9d431fab7bf37dbf05c321b07773cbb727689269f7aa966f4eee4f8877ba2304488ef7b11bb440cfe0e0423490fa319560202806beb0cb4e04ceb2f8b94109

data/lib/autotrace/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Autotrace
-  VERSION = "0.1.9"
+  VERSION = "0.1.11"
 end

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: autotrace
 version: !ruby/object:Gem::Version
-  version: 0.1.9
+  version: 0.1.11
 platform: ruby
 authors:
 - Dylan Player
-autorequire:
-bindir: exe
+bindir: bin
 cert_chain: []
-date: 2025-04-11 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ffi
@@ -35,22 +34,12 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".rubocop.yml"
-- ".ruby-version"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
 - LICENSE.txt
 - README.md
-- Rakefile
-- examples/Dockerfile
-- examples/README.md
-- examples/run.sh
-- examples/sample.png
-- examples/trace_example.rb
 - lib/autotrace.rb
 - lib/autotrace/ffi.rb
 - lib/autotrace/version.rb
-- rubygems_attestation_patch.rb
 homepage: https://github.com/851-labs/autotrace
 licenses:
 - MIT
@@ -58,7 +47,6 @@ metadata:
   homepage_uri: https://github.com/851-labs/autotrace
   source_code_uri: https://github.com/851-labs/autotrace
   changelog_uri: https://github.com/851-labs/autotrace/blob/main/CHANGELOG.md
-post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -73,8 +61,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.23
-signing_key:
+rubygems_version: 3.6.7
 specification_version: 4
 summary: Ruby bindings for the Autotrace library
 test_files: []

data/.rubocop.yml

@@ -1,29 +0,0 @@
-AllCops:
-  TargetRubyVersion: 3.0
-
-Style/StringLiterals:
-  EnforcedStyle: double_quotes
-
-Style/StringLiteralsInInterpolation:
-  EnforcedStyle: double_quotes
-
-Metrics/MethodLength:
-  Enabled: false
-
-Metrics/ClassLength:
-  Enabled: false
-
-Metrics/ModuleLength:
-  Enabled: false
-
-Metrics/CyclomaticComplexity:
-  Enabled: false
-
-Metrics/AbcSize:
-  Enabled: false
-
-Metrics/ParameterLists:
-  Enabled: false
-
-Metrics/PerceivedComplexity:
-  Enabled: false

data/.ruby-version

@@ -1 +0,0 @@
-3.3.5

data/CODE_OF_CONDUCT.md

@@ -1,132 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official email address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[INSERT CONTACT METHOD].
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations

data/Rakefile

@@ -1,12 +0,0 @@
-# frozen_string_literal: true
-
-require "bundler/gem_tasks"
-require "minitest/test_task"
-
-Minitest::TestTask.create
-
-require "rubocop/rake_task"
-
-RuboCop::RakeTask.new
-
-task default: %i[test rubocop]

data/examples/Dockerfile

@@ -1,93 +0,0 @@
-FROM ruby:3.3.5-slim
-
-# Install dependencies for Autotrace based on official build script
-RUN apt-get update && apt-get install -y \
-  build-essential \
-  git \
-  libmagickcore-dev \
-  autotools-dev \
-  autopoint \
-  diffutils \
-  libtool \
-  intltool \
-  libpng-dev \
-  libexif-dev \
-  libtiff5-dev \
-  libjpeg-dev \
-  libxml2-dev \
-  libbz2-dev \
-  libpstoedit-dev \
-  libfreetype6-dev \
-  libpstoedit0c2a \
-  libbz2-1.0 \
-  libgd3 \
-  libffi-dev \
-  pkg-config \
-  curl \
-  wget \
-  && rm -rf /var/lib/apt/lists/*
-
-# Clone and build Autotrace
-WORKDIR /tmp
-RUN git clone https://github.com/autotrace/autotrace.git && \
-  cd autotrace && \
-  ./autogen.sh && \
-  ./configure --prefix=/usr && \
-  make && \
-  make install && \
-  ldconfig && \
-  cd .. && \
-  rm -rf autotrace
-
-# Set up working directory for the application
-WORKDIR /app
-
-# Create output directory
-RUN mkdir -p /app/output
-
-# Copy the entire gem source code to the container
-COPY . /app/autotrace-gem/
-
-# Install required dependencies for the gem
-RUN gem install ffi -v "~> 1.17.1"
-
-# Copy the example files to /app
-COPY examples/trace_example.rb /app/trace_example.rb
-COPY examples/run.sh /app/run.sh
-
-# Make the run script executable
-RUN chmod +x /app/run.sh
-
-# Set RUBYLIB environment variable to include the autotrace gem lib directory
-ENV RUBYLIB="/app/autotrace-gem/lib:${RUBYLIB}"
-
-# Print information about the available libraries
-RUN ldconfig -p | grep "libgobject\\|libglib\\|libMagickCore\\|libpstoedit\\|libpng"
-
-# Set working directory back to /app
-WORKDIR /app
-
-# Find the locations of the required libraries for debugging
-RUN echo "Checking for required libraries:" && \
-  find /usr/lib -name "libautotrace*" && \
-  find /usr/local/lib -name "libautotrace*" && \
-  ldconfig -p | grep autotrace
-
-# Verify that we can load the autotrace gem with better error handling
-RUN ruby -e "begin; \
-  require 'autotrace'; \
-  puts 'Autotrace gem loaded successfully!'; \
-  rescue LoadError => e; \
-  puts \"LoadError: #{e.message}\"; \
-  exit 1; \
-  rescue => e; \
-  puts \"Error: #{e.class.name} - #{e.message}\"; \
-  puts e.backtrace; \
-  exit 1; \
-  end"
-
-# Set the entry point to the shell script
-ENTRYPOINT ["/app/run.sh"]
-
-# The sample.png should be mounted from the host
-# Example: docker run -v $(pwd)/examples/sample.png:/app/sample.png -v $(pwd)/output:/app/output autotrace-example

data/examples/README.md

@@ -1,62 +0,0 @@
-# Autotrace Examples
-
-This directory contains examples demonstrating how to use the Autotrace gem.
-
-## Contents
-
-- `Dockerfile` - Docker setup for running Autotrace
-- `trace_example.rb` - Example Ruby script showing various tracing options
-- `sample.png` - Sample image for the examples
-
-## Running with Docker
-
-The provided Dockerfile sets up a complete environment for running Autotrace.
-
-### Build the Docker image
-
-```bash
-docker build -t autotrace-example -f examples/Dockerfile .
-```
-
-### Run the container with the sample image
-
-```bash
-# Create a directory to store output files
-mkdir -p output
-
-# Run the container with the sample image mounted
-docker run -v $(pwd)/examples/sample.png:/app/sample.png -v $(pwd)/output:/app/output autotrace-example
-```
-
-### Using your own images
-
-You can convert your own images by mounting them to the container:
-
-```bash
-docker run -v /path/to/your/image.png:/app/sample.png -v $(pwd)/output:/app/output autotrace-example
-```
-
-## Running the Ruby Example Directly
-
-If you have Autotrace installed on your system, you can run the example script directly:
-
-```bash
-cd examples
-ruby trace_example.rb
-```
-
-Make sure you have the `sample.png` file in the same directory as the script.
-
-## Output
-
-The traced vector files will be created in the same directory as the input file, with the appropriate extension:
-
-- `sample.svg` - SVG vector output
-- `sample.eps` - EPS vector output (if you run Example 3)
-
-## Additional Resources
-
-For more information about Autotrace and its options, see:
-
-- [Autotrace GitHub Repository](https://github.com/autotrace/autotrace)
-- [Ruby Gem Documentation](https://github.com/851-labs/autotrace)

data/examples/run.sh

@@ -1,28 +0,0 @@
-#!/bin/bash
-
-echo "==================================================="
-echo "Autotrace - Converting raster images to vector graphics"
-echo "==================================================="
-
-if [ ! -f /app/sample.png ]; then
-  echo "Error: sample.png not found in /app directory."
-  echo "Please mount your image to /app/sample.png:"
-  echo "  docker run -v /path/to/your/image.png:/app/sample.png autotrace-example"
-  exit 1
-fi
-
-echo "Found image: /app/sample.png"
-echo "Running trace script..."
-echo "==================================================="
-
-# Run the Ruby example script
-ruby /app/trace_example.rb
-
-# Copy output files to output directory
-cp /app/*.svg /app/output/ 2>/dev/null || true
-cp /app/*.eps /app/output/ 2>/dev/null || true
-
-echo "==================================================="
-echo "Process complete!"
-echo "Output files can be found in the mounted output directory"
-echo "===================================================" 

data/examples/trace_example.rb

@@ -1,57 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-puts "Ruby Version: #{RUBY_VERSION}"
-puts "Load Path: #{$LOAD_PATH.join(":")}"
-puts "Current Directory: #{Dir.pwd}"
-puts "Files in /app/autotrace-gem/lib: #{Dir.glob("/app/autotrace-gem/lib/**/*")}"
-
-begin
-  puts "Attempting to require autotrace..."
-  require "autotrace"
-  puts "Successfully loaded autotrace!"
-rescue LoadError => e
-  puts "Error loading autotrace: #{e.message}"
-  puts "Try loading from direct path..."
-  require_relative "/app/autotrace-gem/lib/autotrace"
-  puts "Successfully loaded autotrace from direct path!"
-end
-
-# This example demonstrates how to use the Autotrace gem to convert
-# a raster image to a vector format with various options.
-
-def trace_with_options(input_file, options = {})
-  puts "Converting #{input_file} with options: #{options.inspect}"
-
-  # Trace the image with the specified options
-  result = Autotrace.trace_image(
-    input_file,
-    **options
-  )
-
-  puts "Conversion complete! Output file: #{result.path}"
-
-  # Return the result file
-  result
-end
-
-# Example 1: Simple conversion to SVG
-puts "Example 1: Simple conversion to SVG"
-trace_with_options("sample.png", output_suffix: "svg")
-
-# Example 2: Conversion with custom options
-puts "\nExample 2: Conversion with custom options"
-trace_with_options("sample.png",
-                   output_suffix: "svg",
-                   background_color: "FFFFFF",  # White background
-                   error_threshold: 1.0,        # Lower error threshold for more detail
-                   despeckle_level: 2,          # Remove small artifacts
-                   preserve_width: true,        # Preserve line widths
-                   centerline: false,           # Don't trace along centerline
-                   noise_removal: 0.95) # Remove noise while preserving detail
-
-# Example 3: Convert to EPS format
-puts "\nExample 3: Convert to EPS format"
-trace_with_options("sample.png", output_suffix: "eps")
-
-puts "\nAll conversions completed successfully!"

data/rubygems_attestation_patch.rb

@@ -1,50 +0,0 @@
-# frozen_string_literal: true
-
-return if RUBY_ENGINE == "jruby"
-return unless defined?(Gem)
-
-require "rubygems/commands/push_command"
-
-Gem::Commands::PushCommand.prepend(Module.new do
-  def send_push_request(name, args)
-    return super if options[:attestations]&.any? || @host != "https://rubygems.org"
-
-    begin
-      send_push_request_with_attestation(name, args)
-    rescue StandardError => e
-      alert_warning "Failed to push with attestation, retrying without attestation.\n#{e.full_message}"
-      super
-    end
-  end
-
-  def send_push_request_with_attestation(name, args)
-    attestation = attest!(name)
-    if options[:attestations]
-      options[:attestations] << attestation
-      send_push_request(name, args)
-    else
-      rubygems_api_request(*args, scope: get_push_scope) do |request|
-        request.set_form([
-                           ["gem", Gem.read_binary(name), { filename: name, content_type: "application/octet-stream" }],
-                           ["attestations", "[#{Gem.read_binary(attestation)}]", { content_type: "application/json" }]
-                         ], "multipart/form-data")
-        request.add_field "Authorization", api_key
-      end
-    end
-  end
-
-  def attest!(name)
-    require "open3"
-    bundle = "#{name}.sigstore.json"
-    env = defined?(Bundler.unbundled_env) ? Bundler.unbundled_env : ENV.to_h
-    out, st = Open3.capture2e(
-      env,
-      Gem.ruby, "-S", "gem", "exec",
-      "sigstore-cli:0.2.1", "sign", name, "--bundle", bundle,
-      unsetenv_others: true
-    )
-    raise Gem::Exception, "Failed to sign gem:\n\n#{out}" unless st.success?
-
-    bundle
-  end
-end)