DOCSLIB.ORG

GL-Get: a Dependency Manager for Software Projects Jordi Vilalta Prat

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
GL-Get: a Dependency Manager for Software Projects Jordi Vilalta Prat Facultat d'Informàtica de Barcelona (FIB) Universitat Politècnica de Catalunya (UPC) Barcelona School of Informatics BarcelonaTech GL-Get: A dependency manager for software projects Jordi Vilalta Prat September 2016 Director: Lluís Solano Albajes Department of Computer science (CS) Informatics Engineering (2003) 2 Thanks This is the end of a very important phase for me, and it wouldn’t have been possible for me to reach it without the help of many great people. Erica and litle Aina, who help me wake up every day. My parents for their unconditional support. My coworkers in general, for making me want to go to work everyday… even when you ask me “How’s GL-Get going? Already finished?” The GL-Get team: Albert, Jeremy and Alex (just pish to master!) And the rest of the company: you rock! 3 4 Table of contents Table of figures....................................................................................................................................8 Table of tables......................................................................................................................................9 Part 1. Introduction............................................................................................................................11 1. Preamble....................................................................................................................................13 1.1. Context...............................................................................................................................13 1.2. Motivation..........................................................................................................................14 1.3. Objectives...........................................................................................................................15 1.4. Document structure............................................................................................................15 2. Beginnings.................................................................................................................................17 2.1. Initial status........................................................................................................................17 2.2. Team...................................................................................................................................17 2.3. Programming languages.....................................................................................................17 Part 2. Development..........................................................................................................................19 3. Specification..............................................................................................................................21 3.1. Problem..............................................................................................................................21 3.1.1. Sharing code...............................................................................................................21 3.1.2. Versioning...................................................................................................................22 3.1.3. Project file creation....................................................................................................23 3.1.4. Continuous integration...............................................................................................25 3.2. Analysis of the existing tools.............................................................................................25 3.2.1. System package managers..........................................................................................26 3.2.2. Language package managers......................................................................................27 3.2.3. Project dependency managers....................................................................................28 3.2.4. Project file creators.....................................................................................................28 3.2.5. Build tools..................................................................................................................28 3.2.6. Continuous integration tools......................................................................................28 3.3. Requirements analysis........................................................................................................29 3.3.1. Functional requirements.............................................................................................29 3.3.2. Non-functional requirements......................................................................................32 3.4. Used tools...........................................................................................................................34 3.5. Use cases............................................................................................................................35 3.5.1. Actors..........................................................................................................................35 3.5.2. Use case diagram........................................................................................................35 3.5.3. Use case description...................................................................................................37 4. Design........................................................................................................................................43 4.1. Concepts.............................................................................................................................43 4.2. System architecture............................................................................................................44 4.3. Application architecture.....................................................................................................46 4.3.1. Actions and command line options............................................................................46 4.3.2. Configuration..............................................................................................................47 4.3.3. Logging......................................................................................................................48 4.3.4. Platform specification.................................................................................................49 4.3.5. VCS abstraction..........................................................................................................52 4.3.6. Embedded Premake integration..................................................................................54 4.3.7. Embedded scripts.......................................................................................................54 4.3.8. Source extractor..........................................................................................................55 4.3.9. Build system...............................................................................................................55 5 4.3.10. Remote build system................................................................................................56 4.3.11. Package definition....................................................................................................57 4.3.12. Manifest....................................................................................................................58 4.3.13. Package cache...........................................................................................................60 4.3.14. Premake extension and translation tree....................................................................62 4.3.15. Package resolution....................................................................................................63 4.3.16. Package checkout.....................................................................................................64 4.3.17. Workspace................................................................................................................67 5. Implementation..........................................................................................................................69 5.1. Lua code.............................................................................................................................69 5.1.1. Arguments checking...................................................................................................69 5.1.2. Modules......................................................................................................................69 5.1.3. Classes........................................................................................................................71 5.1.4. Error handling.............................................................................................................73 5.2. C/C++ code........................................................................................................................75 5.3. Standalone executable........................................................................................................76 5.3.1. Embedded scripts.......................................................................................................76 5.3.2. Dependencies..............................................................................................................77 5.3.3. Main application.........................................................................................................78
Load more

Recommended publications
  • BSD – Alternativen Zu Linux
    ∗BSD { Alternativen zu Linux Karl Lockhoff March 19, 2015 Inhaltsverzeichnis I Woher kommt BSD? I Was ist BSD? I Was ist sind die Unterschiede zwischen FreeBSD, NetBSD und OpenBSD? I Warum soll ich *BSD statt Linux einsetzen? I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I 1978 I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den
    [Show full text]
  • Opensource Software in Mac OS X V. Zhhuta
    Foss Lviv 2013 191 - Linux VM з Wordpress на Azure під’єднано до SQL-бази в приватному центрі обробки даних. Як бачимо, бізнес Microsoft вже дуже сильно зав'язаний на Open Source! Далі в доповіді будуть розглянуті подробиці інтероперабельності платформ з Linux Server, Apache Hadoop, Java, PHP, Node.JS, MongoDb, і наостанок дізнаємося про цікаві Open Source-розробки Microsoft Research. OpenSource Software in Mac OS X V. Zhhuta UK2 LImIted t/a VPS.NET, [email protected] Max OS X stem from Unix: bSD. It contains a lot of things that are common for Unix systems. Kernel, filesystem and base unix utilities as well as it's own package managers. It's not a secret that Mac OS X has a bSD kernel Darwin. The raw Mac OS X won't provide you with all power of Unix but this could be easily fixed: install package manager. There are 3 package manager: MacPorts, Fink and Homebrew. To dive in OpenSource world of mac os x we would try to install lates version of bash, bash-completion and few other utilities. Where we should start? First of all you need to install on you system dev-tools: Xcode – native development tools that contain GCC and libraries. Next step: bring a GIU – X11 into your system. Starting from Mac OS 10.8 X11 is not included in base-installation and it's need to install Xquartz(http://xquartz.macosforge.org). Now it's time to look closely to package managers MacPorts Site: www.macports.org Latest MacPorts release: 2.1.3 Number of ports: 16740 MacPorts born inside Apple in 2002.
    [Show full text]
  • GNU Guix Cookbook Tutorials and Examples for Using the GNU Guix Functional Package Manager
    GNU Guix Cookbook Tutorials and examples for using the GNU Guix Functional Package Manager The GNU Guix Developers Copyright c 2019 Ricardo Wurmus Copyright c 2019 Efraim Flashner Copyright c 2019 Pierre Neidhardt Copyright c 2020 Oleg Pykhalov Copyright c 2020 Matthew Brooks Copyright c 2020 Marcin Karpezo Copyright c 2020 Brice Waegeneire Copyright c 2020 Andr´eBatista Copyright c 2020 Christine Lemmer-Webber Copyright c 2021 Joshua Branson Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Table of Contents GNU Guix Cookbook ::::::::::::::::::::::::::::::: 1 1 Scheme tutorials ::::::::::::::::::::::::::::::::: 2 1.1 A Scheme Crash Course :::::::::::::::::::::::::::::::::::::::: 2 2 Packaging :::::::::::::::::::::::::::::::::::::::: 5 2.1 Packaging Tutorial:::::::::::::::::::::::::::::::::::::::::::::: 5 2.1.1 A \Hello World" package :::::::::::::::::::::::::::::::::: 5 2.1.2 Setup:::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.1.2.1 Local file ::::::::::::::::::::::::::::::::::::::::::::: 8 2.1.2.2 `GUIX_PACKAGE_PATH' ::::::::::::::::::::::::::::::::: 9 2.1.2.3 Guix channels ::::::::::::::::::::::::::::::::::::::: 10 2.1.2.4 Direct checkout hacking:::::::::::::::::::::::::::::: 10 2.1.3 Extended example ::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Table of Contents Modules and Packages
    Table of Contents Modules and Packages...........................................................................................1 Software on NAS Systems..................................................................................................1 Using Software Packages in pkgsrc...................................................................................4 Using Software Modules....................................................................................................7 Modules and Packages Software on NAS Systems UPDATE IN PROGRESS: Starting with version 2.17, SGI MPT is officially known as HPE MPT. Use the command module load mpi-hpe/mpt to get the recommended version of MPT library on NAS systems. This article is being updated to reflect this change. Software programs on NAS systems are managed as modules or packages. Available programs are listed in tables below. Note: The name of a software module or package may contain additional information, such as the vendor name, version number, or what compiler/library is used to build the software. For example: • comp-intel/2016.2.181 - Intel Compiler version 2016.2.181 • mpi-sgi/mpt.2.15r20 - SGI MPI library version 2.15r20 • netcdf/4.4.1.1_mpt - NetCDF version 4.4.1.1, built with SGI MPT Modules Use the module avail command to see all available software modules. Run module whatis to view a short description of every module. For more information about a specific module, run module help modulename. See Using Software Modules for more information. Available Modules (as
    [Show full text]
  • Getting Started Guide for Freebsd Release 18.11.11
    Getting Started Guide for FreeBSD Release 18.11.11 Jan 20, 2021 CONTENTS 1 Introduction 1 1.1 Documentation Roadmap...............................1 2 Installing DPDK from the Ports Collection3 2.1 Installing the DPDK FreeBSD Port..........................3 2.2 Compiling and Running the Example Applications.................3 3 Compiling the DPDK Target from Source6 3.1 System Requirements.................................6 3.2 Install the DPDK and Browse Sources........................7 3.3 Installation of the DPDK Target Environments...................7 3.4 Browsing the Installed DPDK Environment Target.................8 3.5 Loading the DPDK contigmem Module.......................8 3.6 Loading the DPDK nic_uio Module..........................9 4 Compiling and Running Sample Applications 12 4.1 Compiling a Sample Application........................... 12 4.2 Running a Sample Application............................ 13 4.3 Running DPDK Applications Without Root Privileges............... 14 5 EAL parameters 15 5.1 Common EAL parameters.............................. 15 5.2 FreeBSD-specific EAL parameters.......................... 17 i CHAPTER ONE INTRODUCTION This document contains instructions for installing and configuring the Data Plane Development Kit (DPDK) software. It is designed to get customers up and running quickly and describes how to compile and run a DPDK application in a FreeBSD application (bsdapp) environment, without going deeply into detail. For a comprehensive guide to installing and using FreeBSD, the following handbook is available from the FreeBSD Documentation Project: FreeBSD Handbook. Note: The DPDK is now available as part of the FreeBSD ports collection. Installing via the ports collection infrastructure is now the recommended way to install the DPDK on FreeBSD, and is documented in the next chapter, Installing DPDK from the Ports Collection.
    [Show full text]
  • Absolute BSD—The Ultimate Guide to Freebsd Table of Contents Absolute BSD—The Ultimate Guide to Freebsd
    Absolute BSD—The Ultimate Guide to FreeBSD Table of Contents Absolute BSD—The Ultimate Guide to FreeBSD............................................................................1 Dedication..........................................................................................................................................3 Foreword............................................................................................................................................4 Introduction........................................................................................................................................5 What Is FreeBSD?...................................................................................................................5 How Did FreeBSD Get Here?..................................................................................................5 The BSD License: BSD Goes Public.......................................................................................6 The Birth of Modern FreeBSD.................................................................................................6 FreeBSD Development............................................................................................................7 Committers.........................................................................................................................7 Contributors........................................................................................................................8 Users..................................................................................................................................8
    [Show full text]
  • Free Software for the Modelling and Simulation of a Mini-UAV an Analysis
    Mathematics and Computers in Science and Industry Free Software for the Modelling and Simulation of a mini-UAV An Analysis Tomáš Vogeltanz, Roman Jašek Department of Informatics and Artificial Intelligence Tomas Bata University in Zlín, Faculty of Applied Informatics nám. T.G. Masaryka 5555, 760 01 Zlín, CZECH REPUBLIC [email protected], [email protected] Abstract—This paper presents an analysis of free software Current standards for handling qualities apply to only which can be used for the modelling and simulation of a mini- piloted aircraft and there are no specific standards for UAV UAV (Unmanned Aerial Vehicle). Every UAV design, handling qualities. Relevant article discussing dynamic stability construction, implementation and test is unique and presents and handling qualities for small UAVs is [4]. [2] different challenges to engineers. Modelling and simulation software can decrease the time and costs needed to development Any UAV system depends on its mission and range, of any UAV. First part of paper is about general information of however, most UAV systems include: airframe and propulsion the UAV. The fundamentals of airplane flight mechanics are systems, control systems and sensors to fly the UAV, sensors mentioned. The following section briefly describes the modelling to collect information, launch and recovery systems, data links and simulation of the UAV and a flight dynamics model. The to get collected information from the UAV and send main section summarizes free software for the modelling and commands to it, and a ground control station. [3] [5] simulation of the UAV. There is described the following software: Digital Datcom, JSBSim, FlightGear, and OpenEaagles.
    [Show full text]
  • PORTS REPORT by Thomas Abthorpe
    The First PORTS REPORT by Thomas Abthorpe elcome to the inaugural Ports review for completeness. Do not get frustrated; sometimes a port has to be tweaked a couple of Report column for the new times before it compiles cleanly. WFreeBSD Journal. I am Thomas Abthorpe, the FreeBSD Ports Management WHAT’S NEW IN THE PORTS TREE? Team secretary, aka portmgr-secretary@. The nature of the ports tree is that it is forever It seemed to be a natural fit for me to be evolving, growing, and being updated with new asked to do this column, as I take care of software. From time to time, notable changes are inserted into the infrastructure that improve most of the correspondence for the team. and/or alter how ports are built. In July 2013, So what can you look forward to reading in pkg_install stopped being built on 10-CUR- the Ports Report? It will be a summary of RENT, this was done in anticipation of pkng. In September 2013, Stack Protector support was recent activity in the Ports infrastructure, introduced for amd64 and i386 in 10-CURRENT. news in the world of Ports, tips and tricks, One of the newest additions to the infrastruc- plus whatever bits of trivia I can slip in. ture is staging, whichg allows a port to be built into staged directory, instead of getting installed into a production environment. Among RESOURCES TO BUILD AND other functionality, this allows a package to be TEST YOUR PORTS created and bundled with a non-privileged eing a porter is one of the easiest ways to con- account.
    [Show full text]
  • Introduction to the Nix Package Manager
    Introduction Nix concepts Usage examples Conclusion Introduction to the Nix Package Manager Millian Poquet 2021-05-12 — Datamove (Inria) seminar 1 / 16 Introduction Nix concepts Usage examples Conclusion Why Nix? Control your software environment! Programs/libraries/scripts/configurations + versions Why is it important for us? Use/develop/test/distribute software Manually install many dependencies? No, just type nix-shell Shared env for whole team (tunable) and test machines Bug only on my machine? Means this is hardware or OS related Reproducible research Repeat experiment in exact same environment Introduce or test variation 2 / 16 Introduction Nix concepts Usage examples Conclusion What is Nix? Nix: package manager Download and install packages Shell into well-defined environment (like virtualenv) Transactional (rollback works) Cross-platform: Linux, macOS, Windows (WSL) Nix: programming language Define packages Define environments (set of packages) Functional, DSL NixOS: Linux distribution Declarative system configuration Uses the Nix language Transactional (rollback still works) 3 / 16 Introduction Nix concepts Usage examples Conclusion Nix in numbers Started in 2003 Nix 1: 10k commits, 28k C++ LOC Nixpkgs 2: 285k commits, 55k packages 3 1. https://github.com/NixOS/nix 2. https://github.com/NixOS/nixpkgs 3. https://repology.org/repositories/statistics 4 / 16 Introduction Nix concepts Usage examples Conclusion Presentation summary 2 Nix concepts 3 Usage examples 4 Conclusion 5 / 16 Introduction Nix concepts Usage examples Conclusion Traditional
    [Show full text]
  • Automatic Dependency Management for Scientific Applications on Clusters
    Automatic Dependency Management for Scientific Applications on Clusters Ben Tovar, Nicholas Hazekamp, Nathaniel Kremer-Herman, and Douglas Thain btovar,nhazekam,nkremerh,dthain @nd.edu { } Department of Computer Science and Engineering University of Notre Dame Abstract—Software installation remains a challenge in scien- are unprivileged, and multiple incompatible versions may need tific computing. End users require custom software stacks that to exist simultaneously. are not provided through commodity channels. The resulting To address this problem, we present VC3-Builder, a user- effort needed to install software delays research in the first place, and creates friction for moving applications to new resources level system for managing software dependencies across mul- and new users. Ideally, end-users should be able to manage their tiple clusters. VC3-Builder shares some elements of design own software stacks without requiring administrator privileges. with recent systems such as Nix [8] and Spack [10], but it To that end, we describe VC3-Builder, a tool for deploying is more suited for rapid deployment by exploiting pre-existing software environments automatically on clusters. Its primary software where available and using the resources of the cluster application comes in cloud and opportunistic computing, where deployment must be performed in batch as a side effect of job itself to perform parallel and distributed builds. execution. VC3-Builder uses workflow technologies as a means We demonstrate VC3-Builder by several case studies of of exploiting cluster resources for building in a portable way. We complex applications that present a challenge for users to build demonstrate the use of VC3-Builder on three applications with and deploy manually: the MAKER bioinformatics pipeline, the complex dependencies: MAKER, Octave, and CVMFS, building CVMFS distributed filesystem, and the Octave mathematics and running on three different cluster facilities in sequential, parallel, and distributed modes.
    [Show full text]
  • Soloud Audio Engine
    SoLoud Audio Engine Jari Komppa May 21, 2014 Contents 1 Introduction 2 1.1 How Easy? ..................................... 2 1.2 How Free? ..................................... 2 1.3 How Powerful? ................................... 3 1.4 There’s a Catch, Right? .............................. 3 2 Legal 4 2.1 SoLoud Proper ................................... 4 2.2 OGG Support ................................... 4 2.3 Speech Synthesizer ................................ 4 2.4 Fast Fourier Transform (FFT) ........................... 5 2.5 Sfxr ........................................ 5 2.6 Libmodplug .................................... 6 3 Quick Start 7 3.1 Download SoLoud ................................. 7 3.2 Add files to your project ............................. 7 3.3 Include files .................................... 7 3.4 Variables ..................................... 7 3.5 Initialize SoLoud .................................. 7 3.6 Set up sound sources ............................... 8 3.7 Play sounds .................................... 8 3.8 Take control of the sound ............................. 8 3.9 Cleanup ...................................... 8 3.10 Enjoy ....................................... 8 4 Premake 9 5 Concepts 10 5.1 Back end ..................................... 10 5.2 Channel ...................................... 10 5.3 Stream ...................................... 10 5.4 Clipping ...................................... 10 5.5 Sample ...................................... 11 5.6 Sample Rate ...................................
    [Show full text]
  • Le 2016-07-20 REQUEST for PROPOSAL DEMANDE DE PROPOSITION
    1 1 RETURN BIDS TO: Title - Sujet RETOURNER LES SOUMISSIONS À: Visually Statistically Intelligent Bid Receiving - PWGSC / Réception des Solicitation No. - N° de l'invitation Date soumissions - TPSGC 45045-140073/C 2016-06-10 11 Laurier St. / 11, rue Laurier Client Reference No. - N° de référence du client Place du Portage, Phase III 000006399 Core 0B2 / Noyau 0B2 GETS Reference No. - N° de référence de SEAG Gatineau PW-$$EE-002-30267 Quebec K1A 0S5 File No. - N° de dossier CCC No./N° CCC - FMS No./N° VME Bid Fax: (819) 997-9776 002ee.45045-140073 Solicitation Closes - L'invitation prend fin Time Zone Fuseau horaire at - à 02:00 PM Eastern Daylight Saving REQUEST FOR PROPOSAL on - le 2016-07-20 Time EDT DEMANDE DE PROPOSITION F.O.B. - F.A.B. Proposal To: Public Works and Government Services Canada Plant-Usine: Destination: Other-Autre: We hereby offer to sell to Her Majesty the Queen in right Address Enquiries to: - Adresser toutes questions à: Buyer Id - Id de l'acheteur of Canada, in accordance with the terms and conditions Gabriel (ee div), Peter 002ee set out herein, referred to herein or attached hereto, the Telephone No. - N° de téléphone FAX No. - N° de FAX goods, services, and construction listed herein and on any (873) 469-4654 ( ) ( ) - attached sheets at the price(s) set out therefor. Destination - of Goods, Services, and Construction: Proposition aux: Travaux Publics et Services Destination - des biens, services et construction: Gouvernementaux Canada Nous offrons par la présente de vendre à Sa Majesté la Reine du chef du Canada, aux conditions énoncées ou Specified Herein incluses par référence dans la présente et aux annexes Précisé dans les présentes ci-jointes, les biens, services et construction énumérés ici sur toute feuille ci-annexée, au(x) prix indiqué(s).
    [Show full text]