DOCSLIB.ORG

Debian Policy Manual Release 4.6.0.1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Debian Policy Manual Release 4.6.0.1 Debian Policy Manual Release 4.6.0.1 The Debian Policy Mailing List Aug 18, 2021 CONTENTS 1 About this manual 3 1.1 Scope ................................................... 3 1.2 New versions of this document ...................................... 4 1.3 Authors and Maintainers ......................................... 4 1.3.1 Early history ........................................... 4 1.3.2 Current process ......................................... 4 1.3.3 Improvements .......................................... 5 1.4 Related documents ............................................ 5 1.5 Definitions ................................................ 5 1.6 Translations ................................................ 6 2 The Debian Archive 7 2.1 The Debian Free Software Guidelines .................................. 7 2.2 Archive areas ............................................... 8 2.2.1 The main archive area ...................................... 8 2.2.2 The contrib archive area ..................................... 8 2.2.3 The non-free archive area .................................... 9 2.3 Copyright considerations ......................................... 9 2.4 Sections .................................................. 10 2.5 Priorities ................................................. 10 3 Binary packages 13 3.1 The package name ............................................ 13 3.1.1 Packages with potentially offensive content ........................... 13 3.2 The version of a package ......................................... 14 3.2.1 Version numbers based on dates ................................. 14 3.2.2 Uniqueness of version numbers ................................. 14 3.3 The maintainer of a package ....................................... 15 3.4 The description of a package ....................................... 15 3.4.1 The single line synopsis ..................................... 16 3.4.2 The extended description .................................... 16 3.5 Dependencies ............................................... 16 3.6 Virtual packages ............................................. 16 3.7 Base system ................................................ 17 3.8 Essential packages ............................................ 17 3.9 Maintainer Scripts ............................................ 17 3.9.1 Prompting in maintainer scripts ................................. 18 4 Source packages 19 4.1 Standards conformance .......................................... 19 i 4.2 Package relationships ........................................... 19 4.3 Changes to the upstream sources ..................................... 20 4.4 Debian changelog: debian/changelog ............................... 20 4.5 Copyright: debian/copyright ................................... 22 4.6 Error trapping in makefiles ........................................ 22 4.7 Time Stamps ............................................... 22 4.8 Restrictions on objects in source packages ................................ 22 4.9 Main building script: debian/rules ................................. 22 4.9.1 debian/rules and DEB_BUILD_OPTIONS ........................ 25 4.9.2 debian/rules and Rules-Requires-Root ...................... 26 4.10 Variable substitutions: debian/substvars ............................. 27 4.11 Upstream source location: debian/watch .............................. 27 4.12 Generated files list: debian/files .................................. 28 4.13 Embedded code copies .......................................... 28 4.14 Source package handling: debian/README.source ........................ 28 4.15 Reproducibility .............................................. 29 4.16 Missing sources: debian/missing-sources ........................... 29 4.17 Vendor-specific patch series ....................................... 29 5 Control files and their fields 31 5.1 Syntax of control files ........................................... 31 5.2 Source package control files – debian/control ........................... 32 5.3 Binary package control files – DEBIAN/control ........................... 33 5.4 Debian source control files – .dsc .................................... 34 5.5 Debian changes files – .changes .................................... 34 5.6 List of fields ............................................... 35 5.6.1 Source ............................................. 35 5.6.2 Maintainer ......................................... 35 5.6.3 Uploaders .......................................... 36 5.6.4 Changed-By ......................................... 36 5.6.5 Section ............................................ 36 5.6.6 Priority ........................................... 36 5.6.7 Package ............................................ 36 5.6.8 Architecture ........................................ 36 5.6.9 Essential .......................................... 37 5.6.10 Package interrelationship fields: Depends, Pre-Depends, Recommends, Suggests, Breaks, Conflicts, Provides, Replaces, Enhances ............... 37 5.6.11 Standards-Version .................................... 37 5.6.12 Version ............................................ 38 5.6.12.1 Epochs should be used sparingly ............................ 39 5.6.13 Description ......................................... 39 5.6.14 Distribution ........................................ 40 5.6.15 Date .............................................. 40 5.6.16 Format ............................................. 40 5.6.17 Urgency ............................................ 40 5.6.18 Changes ............................................ 41 5.6.19 Binary ............................................. 41 5.6.20 Installed-Size ...................................... 41 5.6.21 Files ............................................. 41 5.6.22 Closes ............................................. 42 5.6.23 Homepage ........................................... 42 5.6.24 Checksums-Sha1 and Checksums-Sha256 ....................... 42 5.6.25 DM-Upload-Allowed .................................... 43 5.6.26 Version Control System (VCS) fields .............................. 43 ii 5.6.27 Package-List ........................................ 44 5.6.28 Package-Type ........................................ 44 5.6.29 Dgit .............................................. 44 5.6.30 Testsuite .......................................... 44 5.6.31 Rules-Requires-Root .................................. 45 5.6.31.1 Remarks ........................................ 45 5.6.31.2 Definition of the keywords ............................... 45 5.6.31.3 Provided keywords ................................... 46 5.7 User-defined fields ............................................ 46 5.8 Obsolete fields .............................................. 46 5.8.1 DM-Upload-Allowed .................................... 47 6 Package maintainer scripts and installation procedure 49 6.1 Introduction to package maintainer scripts ................................ 49 6.2 Maintainer scripts idempotency ...................................... 50 6.3 Controlling terminal for maintainer scripts ................................ 50 6.4 Exit status ................................................. 50 6.5 Summary of ways maintainer scripts are called .............................. 50 6.6 Details of unpack phase of installation or upgrade ............................ 52 6.7 Details of configuration .......................................... 55 6.8 Details of removal and/or configuration purging ............................. 55 7 Declaring relationships between packages 57 7.1 Syntax of relationship fields ........................................ 57 7.2 Binary Dependencies - Depends, Recommends, Suggests, Enhances, Pre-Depends .... 59 7.3 Packages which break other packages - Breaks ............................. 60 7.4 Conflicting binary packages - Conflicts ............................... 61 7.5 Virtual packages - Provides ...................................... 62 7.6 Overwriting files and replacing packages - Replaces ......................... 63 7.6.1 Overwriting files in other packages ............................... 63 7.6.2 Replacing whole packages, forcing their removal ........................ 64 7.7 Relationships between source and binary packages - Build-Depends, Build-Depends-Indep, Build-Depends-Arch, Build-Conflicts, Build-Conflicts-Indep, Build- Conflicts-Arch ........................................... 64 7.8 Additional source packages used to build the binary - Built-Using ................. 65 8 Shared libraries 67 8.1 Run-time shared libraries ......................................... 68 8.1.1 ldconfig ........................................... 69 8.2 Shared library support files ........................................ 69 8.3 Static libraries .............................................. 69 8.4 Development files ............................................. 70 8.5 Dependencies between the packages of the same library ......................... 70 8.6 Dependencies between the library and other packages .......................... 70 8.6.1 Generating dependencies on shared libraries .......................... 71 8.6.2 Shared library ABI changes ................................... 72 8.6.3 The symbols system ...................................... 73 8.6.3.1 The symbols files present on the system ....................... 73 8.6.3.2 The symbols File Format .............................. 73 8.6.3.3 Providing a symbols file ............................... 75 8.6.4 The shlibs system
Load more

Recommended publications
  • Debian Developer's Reference Version 12.0, Released on 2021-09-01
    Debian Developer’s Reference Release 12.0 Developer’s Reference Team 2021-09-01 CONTENTS 1 Scope of This Document 3 2 Applying to Become a Member5 2.1 Getting started..............................................5 2.2 Debian mentors and sponsors......................................6 2.3 Registering as a Debian member.....................................6 3 Debian Developer's Duties 9 3.1 Package Maintainer's Duties.......................................9 3.1.1 Work towards the next stable release............................9 3.1.2 Maintain packages in stable .................................9 3.1.3 Manage release-critical bugs.................................. 10 3.1.4 Coordination with upstream developers............................ 10 3.2 Administrative Duties.......................................... 10 3.2.1 Maintaining your Debian information............................. 11 3.2.2 Maintaining your public key.................................. 11 3.2.3 Voting.............................................. 11 3.2.4 Going on vacation gracefully.................................. 12 3.2.5 Retiring............................................. 12 3.2.6 Returning after retirement................................... 13 4 Resources for Debian Members 15 4.1 Mailing lists............................................... 15 4.1.1 Basic rules for use....................................... 15 4.1.2 Core development mailing lists................................. 15 4.1.3 Special lists........................................... 16 4.1.4 Requesting new
    [Show full text]
  • Amateur Radio Software Distributed with (X)Ubuntu LTS Serge Stroobandt, ON4AA
    Amateur Radio Software Distributed with (X)Ubuntu LTS Serge Stroobandt, ON4AA Copyright 2014–2018, licensed under Creative Commons BY-NC-SA Introduction Amateur radio (also called “ham radio”), is a technical hobby Many ham radio stations are highly integrated with computers. Radios are interfaced with com- puters to aid with contact logging, propagation prediction, station spotting, antenna steering, signal (de)modulation and filtering. For many years, amateur radio software has been a bastion of Windows™ ap- plications developed by However, with the advent of the Rasperry Pi, amateur radio hobbyists are slowly but surely discovering GNU/Linux. Most of the software for GNU/Linux is available through package repositories. Such package repositories come by default with the GNU/Linux distribution of your choice. Package management systems offer many benefits in the form of security (you know what you are getting from whom) and ease-of-use (packages are upgraded automatically). No longer does one need to wander the back corners of the internet to find wne or updated software, exposing oneself to the risk of catching a computer virus. A number of GNU/Linux distributions offer freely installable ham-related packages under the “Amateur Radio” section of their main repository. The largest collection of ham radio packages is offeredy b OpenSuse and De- bian-derived distributions like Xubuntu LTS and Linux Mint, to name but a few. Arch Linux may also have whole bunch of ham related software in the Arch User Repository (AUR). 1 Synaptic One way to find and tallins ham radio packages on Debian-derived distros is by using the Synaptic graphical package manager (see Figure 1).
    [Show full text]
  • Beginning Portable Shell Scripting from Novice to Professional
    Beginning Portable Shell Scripting From Novice to Professional Peter Seebach 10436fmfinal 1 10/23/08 10:40:24 PM Beginning Portable Shell Scripting: From Novice to Professional Copyright © 2008 by Peter Seebach All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (pbk): 978-1-4302-1043-6 ISBN-10 (pbk): 1-4302-1043-5 ISBN-13 (electronic): 978-1-4302-1044-3 ISBN-10 (electronic): 1-4302-1044-3 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Frank Pohlmann Technical Reviewer: Gary V. Vaughan Editorial Board: Clay Andres, Steve Anglin, Ewan Buckingham, Tony Campbell, Gary Cornell, Jonathan Gennick, Michelle Lowman, Matthew Moodie, Jeffrey Pepper, Frank Pohlmann, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Project Manager: Richard Dal Porto Copy Editor: Kim Benbow Associate Production Director: Kari Brooks-Copony Production Editor: Katie Stence Compositor: Linda Weidemann, Wolf Creek Press Proofreader: Dan Shaw Indexer: Broccoli Information Management Cover Designer: Kurt Krames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013.
    [Show full text]
  • Leitfaden Für Debian-Betreuer
    Leitfaden für Debian­Betreuer Osamu Aoki, Helge Kreutzmann, and Mechtilde Stehmann August 27, 2021 Leitfaden für Debian­Betreuer by Osamu Aoki, Helge Kreutzmann, and Mechtilde Stehmann Copyright © 2014­2020 Osamu Aoki Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ”Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED ”AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IM­ PLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Diese Anleitung wurde mit den nachfolgenden Dokumenten als Referenz erstellt: • »Making a Debian Package (AKA the Debmake Manual)«, Copyright © 1997 Jaldhar Vyas. • »The New­Maintainer’s Debian Packaging Howto«, Copyright © 1997 Will Lowe. • »Debian­Leitfaden für Neue Paketbetreuer«, Copyright © 1998­2002 Josip Rodin, 2005­2017 Osamu Aoki, 2010 Craig Small und 2010 Raphaël Hertzog. Die neuste Version dieser Anleitung sollte • im Paket debmake­doc und • auf der Debian­Dokumentations­Website verfügbar sein.
    [Show full text]
  • Panstamps Documentation Release V0.5.3
    panstamps Documentation Release v0.5.3 Dave Young 2020 Getting Started 1 Installation 3 1.1 Troubleshooting on Mac OSX......................................3 1.2 Development...............................................3 1.2.1 Sublime Snippets........................................4 1.3 Issues...................................................4 2 Command-Line Usage 5 3 Documentation 7 4 Command-Line Tutorial 9 4.1 Command-Line..............................................9 4.1.1 JPEGS.............................................. 12 4.1.2 Temporal Constraints (Useful for Moving Objects)...................... 17 4.2 Importing to Your Own Python Script.................................. 18 5 Installation 19 5.1 Troubleshooting on Mac OSX...................................... 19 5.2 Development............................................... 19 5.2.1 Sublime Snippets........................................ 20 5.3 Issues................................................... 20 6 Command-Line Usage 21 7 Documentation 23 8 Command-Line Tutorial 25 8.1 Command-Line.............................................. 25 8.1.1 JPEGS.............................................. 28 8.1.2 Temporal Constraints (Useful for Moving Objects)...................... 33 8.2 Importing to Your Own Python Script.................................. 34 8.2.1 Subpackages.......................................... 35 8.2.1.1 panstamps.commonutils (subpackage)........................ 35 8.2.1.2 panstamps.image (subpackage)............................ 35 8.2.2 Classes............................................
    [Show full text]
  • Discrete Cosine Transform for 8X8 Blocks with CUDA
    Discrete Cosine Transform for 8x8 Blocks with CUDA Anton Obukhov [email protected] Alexander Kharlamov [email protected] October 2008 Document Change History Version Date Responsible Reason for Change 0.8 24.03.2008 Alexander Kharlamov Initial release 0.9 25.03.2008 Anton Obukhov Added algorithm-specific parts, fixed some issues 1.0 17.10.2008 Anton Obukhov Revised document structure October 2008 2 Abstract In this whitepaper the Discrete Cosine Transform (DCT) is discussed. The two-dimensional variation of the transform that operates on 8x8 blocks (DCT8x8) is widely used in image and video coding because it exhibits high signal decorrelation rates and can be easily implemented on the majority of contemporary computing architectures. The key feature of the DCT8x8 is that any pair of 8x8 blocks can be processed independently. This makes possible fully parallel implementation of DCT8x8 by definition. Most of CPU-based implementations of DCT8x8 are firmly adjusted for operating using fixed point arithmetic but still appear to be rather costly as soon as blocks are processed in the sequential order by the single ALU. Performing DCT8x8 computation on GPU using NVIDIA CUDA technology gives significant performance boost even compared to a modern CPU. The proposed approach is accompanied with the sample code “DCT8x8” in the NVIDIA CUDA SDK. October 2008 3 1. Introduction The Discrete Cosine Transform (DCT) is a Fourier-like transform, which was first proposed by Ahmed et al . (1974). While the Fourier Transform represents a signal as the mixture of sines and cosines, the Cosine Transform performs only the cosine-series expansion.
    [Show full text]
  • The GNOME Desktop Environment
    The GNOME desktop environment Miguel de Icaza ([email protected]) Instituto de Ciencias Nucleares, UNAM Elliot Lee ([email protected]) Federico Mena ([email protected]) Instituto de Ciencias Nucleares, UNAM Tom Tromey ([email protected]) April 27, 1998 Abstract We present an overview of the free GNU Network Object Model Environment (GNOME). GNOME is a suite of X11 GUI applications that provides joy to users and hackers alike. It has been designed for extensibility and automation by using CORBA and scripting languages throughout the code. GNOME is licensed under the terms of the GNU GPL and the GNU LGPL and has been developed on the Internet by a loosely-coupled team of programmers. 1 Motivation Free operating systems1 are excellent at providing server-class services, and so are often the ideal choice for a server machine. However, the lack of a consistent user interface and of consumer-targeted applications has prevented free operating systems from reaching the vast majority of users — the desktop users. As such, the benefits of free software have only been enjoyed by the technically savvy computer user community. Most users are still locked into proprietary solutions for their desktop environments. By using GNOME, free operating systems will have a complete, user-friendly desktop which will provide users with powerful and easy-to-use graphical applications. Many people have suggested that the cause for the lack of free user-oriented appli- cations is that these do not provide enough excitement to hackers, as opposed to system- level programming. Since most of the GNOME code had to be written by hackers, we kept them happy: the magic recipe here is to design GNOME around an adrenaline response by trying to use exciting models and ideas in the applications.
    [Show full text]
  • Wxwidgets Un Framework Per Realizzare Applicazioni Con Interfaccia Utente Nativa
    wxWidgets un framework per realizzare applicazioni con interfaccia utente nativa relatore Marco Cavallini Libertà I tradizionali gradi di libertà Open Source: libertà di utilizzo gratuito libertà di modifica libertà dalla dipendenza verso un fornitore Con wxWidgets possiamo aggiungere: libertà di utilizzare un'applicazione su qualunque piattaforma ...? 2 Contenuti Contenuti Cos'è wxWidgets? Piattaforme supportate Illustrazioni Per cosa piace wxWidgets? Portabilità API Tools per lo sviluppatore Storia Applicazioni di esempio 3 Cos'è wxWidgets? wxWidgets aiuta nello sviluppo di applicazioni che sono: multi-piattaforma multi-lingua realmente native veloci facili da usare facili da scrivere dall'aspetto professionale free o commerciali robuste 4 Cos'è wxWidgets? (cont'd) wxWidgets consiste di: C++ API (1) un set di librerie, una per piattaforma un manuale di 1700 pagine una collezione di oltre 70 esempi un help viewer e altri tools una comunità di sviluppatori (1) also available for Python, Perl, Basic, JavaScript, Lua, Eiffel 5 Cos'è wxWidgets? (cont'd) Alcune statistiche: oltre 300 classi oltre 5.000 funzioni oltre 1,3 milioni di linee di codice è un prodotto maturo : oltre 10 anni di età costo stimato di sviluppo 41MLN di $ in Dicembre 2001 circa 1.500 sottoscrittori della mailing lists (wxWidgets + wxPython) 6 Piattaforme supportate wxWidgets API wxMSW wxGTK wxX11 wxMotif wxMac wxOS2 Classic or WIN32 GTK+ Xlib Motif/Lesstif Carbon Carbon PM Windows Unix/Linux MacOS 9MacOS X OS/2 Key: Port GUI OS Other variants: Unix variants: wxBase – non-GUI subset of wxWidgets API Linux x86, Linux S/390, wxMGL – port to SciTech's MGL layer OpenBSD, FreeBSD, NetBSD, wxMSW/Univ – WIN32 port using own widget set Solaris, Darwin, AIX, HP-UX, IRIX, wxMSW apps on Wine; wxMSW compiled with Winelib SCI UnixWare, DEC OSF/1 wxGTK/wxX11 on MacOS X under X11 (e.g.
    [Show full text]
  • The C Clustering Library the University of Tokyo, Institute of Medical Science, Human Genome Center
    The C Clustering Library The University of Tokyo, Institute of Medical Science, Human Genome Center Michiel de Hoon, Seiya Imoto, Satoru Miyano 30 August 2019 The C Clustering Library for cDNA microarray data. Copyright c 2002-2005 Michiel Jan Laurens de Hoon This library was written at the Laboratory of DNA Information Analysis, Human Genome Center, Institute of Medical Science, University of Tokyo, 4-6-1 Shirokanedai, Minato-ku, Tokyo 108-8639, Japan. Contact: michiel.dehoon "AT" riken.jp Permission to use, copy, modify, and distribute this software and its documentation with or without modifications and for any purpose and without fee is hereby granted, provided that any copyright notices appear in all copies and that both those copyright notices and this permission notice appear in supporting documentation, and that the names of the contrib- utors or copyright holders not be used in advertising or publicity pertaining to distribution of the software without specific prior permission. THE CONTRIBUTORS AND COPYRIGHT HOLDERS OF THIS SOFTWARE DIS- CLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL THE CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHAT- SOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARIS- ING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. i Table of Contents 1 Introduction ..................................... 1 2 Distance functions............................... 2 2.1 Data handling .................................................. 3 2.2 Weighting ................................................... ... 3 2.3 Missing Values ................................................
    [Show full text]
  • Compiling C Programs
    CSCI 2132: Software Development Lab 6: Exploring bash and C Compilation Synopsis In this lab, you will: • Customize the behaviour your bash shell • Write and compile some simple C programs • Practice the edit-compile-fix cycle using emacs and the shell • Learn to patch programs using diff and patch Contents Overview......................................................................................................2 Step 1: Login and lab setup.................................................................................3 Step 2: The name of your shell.............................................................................3 Step 3: The .bashrc file.....................................................................................3 Step 4: Customize rm ........................................................................................4 Optional Step: Install bashrc.new as your new .bashrc file............................................7 Step 5: Edit .profile .......................................................................................8 Optional Step: Install profile.new as your new .profile file.......................................... 10 Step 6: Write a simple C program.......................................................................... 11 Step 7: Explore exit codes................................................................................... 12 Step 8: diff .................................................................................................. 14 Step 9: patch................................................................................................
    [Show full text]
  • Original File Was Cvddn.Tex
    Paul Bowman Durao email: [email protected] Phone: (301) 412-6312 or SKYPE: paul.durao Maryland / Washington DC / Remote Senior Software Architect / Engineer / Software Developer 30+ years of experience full life-cycle software development Exceptionally well-qualified senior software architect engineer with extensive programming skills. Subject matter expert in applying methodologies, processes, and procedures in the execution of full life-cycle approach. There is no substitute for a proper engineering degree, first-rate hands on experience, and sophisticated problem solving methodology, but it’s not for everyone, and that’s where I shine and come through for the team. Flexible Working Classifications 1. 1099 Contract Worker 2. Corp to Corp Contract Worker 3. Statutory Employee 4. At Will Employee 5. Contract ± Sub Contract W-2 Employee 6. Regular W-2 Employee 7. Remote and work at home preferred 8. Willing to travel part, or full time. Technical Qualifications Languages: C, C++, Java, JavaScript, ( Angular Js, DOJO, JQuery), Html, CSS, Ruby, XML, Perl, Python, lisp, Assembly (ARM/Intel), SQL; Operating Systems: Linux, Unix, BSD, OSX. iOS, Motif, Embedded; Database: PL/SQL, Oracle; Library, Middleware and API’s: Java EE, ROR; Additional skills: Data Modeling; MVC; UML, TDD, O/R mapping; Miscellaneous: 508 Compliance (web accessibility). Career Highlights Work Chronology – Independent consulting, and some full time, sometimes there is a mix. I have done consulting on a full/long time basis too, for NASA and IBM for example, as my skill level has improved relative to the market. I have tended to do more independent contracting work as my skill level, comprehension, and abilities are just different, and more specialized, and therefore higher in fidelity, and in quality (Linux, UNIX, OSX, iOS 8 / xcode 6, development centric, all things UNIX related).
    [Show full text]
  • Sbt-Native-Packager Release 1.0A1
    sbt-native-packager Release 1.0a1 Josh Suereth Sep 18, 2021 Contents 1 Introduction 1 1.1 Goals...................................................1 1.2 Scope...................................................1 1.3 Core Concepts..............................................2 2 Getting Started 5 2.1 Setup...................................................5 2.2 Your first package............................................5 3 Packaging Formats 7 3.1 Universal Plugin.............................................8 3.2 Linux Plugin............................................... 15 3.3 Debian Plugin.............................................. 21 3.4 Rpm Plugin................................................ 25 3.5 Docker Plugin.............................................. 31 3.6 Windows Plugin............................................. 38 3.7 JDKPackager Plugin........................................... 41 3.8 GraalVM Native Image Plugin...................................... 44 4 Project Archetypes 47 4.1 Java Application Archetype....................................... 47 4.2 Java Server Application Archetype................................... 54 4.3 Systemloaders.............................................. 59 4.4 Configuration Archetypes........................................ 62 4.5 Jlink Plugin................................................ 62 4.6 Archetype Cheatsheet.......................................... 64 5 Recipes 69 5.1 Custom Package Formats........................................ 69 5.2 Dealing with long classpaths......................................
    [Show full text]