DOCSLIB.ORG

Mvbluefox3 Technical Manual (Pdf)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mvbluefox3 Technical Manual (Pdf) mvBlueFOX3 Technical Manual English - Version 3.04 i 1.1 About this manual............................................ 1 1.1.1 Goal of the manual ....................................... 1 1.1.2 Contents of the manual..................................... 1 1.2 Imprint.................................................. 2 1.2.1 Introduction ........................................... 3 1.2.2 wxWidgets............................................ 3 1.2.3 Sarissa ............................................. 3 1.2.4 GenICam ............................................ 3 1.2.5 libusb .............................................. 3 1.2.6 libusbK.............................................. 3 1.2.6.1 libusbK license .................................... 3 1.2.7 Doxygen............................................. 4 1.2.7.1 Doxygen license ................................... 4 1.2.8 SHA1 algorithm......................................... 4 1.2.9 Expat .............................................. 5 1.2.9.1 Expat Copyright.................................... 5 1.2.10 CppUnit ............................................ 5 1.2.11 NUnit.............................................. 5 1.2.11.1 NUnit License.................................... 5 1.3 Legal notice............................................... 6 1.3.1 Introduction ........................................... 6 1.3.2 cJSON.............................................. 6 1.3.3 Unity............................................... 6 1.4 Revisions ................................................ 7 1.5 Symbols and Conventions........................................ 8 1.5.1 Explanation of the warnings................................... 8 1.6 Important Information.......................................... 9 1.6.1 Important Safety Instructions.................................. 9 1.6.2 Operating considerations.................................... 9 1.6.2.1 Important Safety Notes................................ 9 1.6.2.2 Handling And Cleaning................................ 10 1.6.2.3 Installing ....................................... 10 1.6.2.4 Optimizing performance and life time......................... 11 1.6.2.5 Connectors...................................... 11 1.6.2.6 Cleaning ....................................... 11 1.6.3 Additional notices........................................ 21 1.6.3.1 For customers in the U.S.A............................... 21 1.6.3.2 For customers in Canada............................... 21 1.6.3.3 Pour utilisateurs au Canada ............................. 21 1.7 Introduction ............................................... 22 1.7.1 Software concept ........................................ 23 1.7.2 Order code nomenclatures ................................... 24 MATRIX VISION GmbH ii 1.7.2.1 mvBlueFOX3-1.................................... 24 1.7.2.2 mvBlueFOX3-M1................................... 25 1.7.2.3 mvBlueFOX3-2.................................... 26 1.7.2.4 mvBlueFOX3-M2................................... 28 1.7.2.5 mvBlueFOX3-3M................................... 30 1.7.2.6 mvBlueFOX3-4.................................... 31 1.7.2.7 mvBlueFOX3-5M................................... 32 1.7.2.8 Ordering code samples................................ 33 1.7.3 What's inside and accessories ................................. 34 1.7.3.1 Accessories for the mvBlueFOX3........................... 35 1.8 Quickstart................................................ 37 1.8.1 System Requirements...................................... 37 1.8.1.1 Host System ..................................... 37 1.8.1.2 Supported Operating Systems............................ 37 1.8.2 Installing The mvGenTL-Acquire Package ........................... 38 1.8.2.1 Windows ....................................... 39 1.8.2.2 Linux ......................................... 42 1.8.3 Connecting The Camera .................................... 45 1.8.3.1 Communicating With The Camera.......................... 45 1.8.3.2 Setting Up The Camera................................ 45 1.8.3.3 About Settings .................................... 46 1.8.4 Driver concept.......................................... 48 1.8.4.1 NeuroCheck Support................................. 49 1.8.4.2 VisionPro Support .................................. 50 1.8.4.3 HALCON Support................................... 50 1.8.4.4 LabVIEW Support................................... 50 1.8.4.5 DirectShow Support ................................. 50 1.8.4.6 Micro-Manager Support................................ 50 1.8.5 Relationship Between Driver, Firmware And SDK ....................... 51 1.8.6 Optimizing USB Performance.................................. 54 1.8.6.1 Checklist for Windows ................................ 54 1.8.6.2 Checklist for Linux .................................. 54 1.8.7 Using USB3 Vision™ Devices In A Docker Container ..................... 56 1.8.7.1 Host Preparation ................................... 57 1.8.7.2 Building A Docker Image............................... 57 1.8.7.3 Starting The Docker Container............................ 58 1.8.7.4 Validation....................................... 59 1.9 Technical Data.............................................. 59 1.9.1 Dimensions ........................................... 59 1.9.1.1 Standard model (mvBlueFOX3-1) .......................... 59 1.9.1.2 Standard model (mvBlueFOX3-2) .......................... 60 1.9.1.3 Model without housing (mvBlueFOX3-M1)...................... 62 MATRIX VISION GmbH iii 1.9.1.4 Model without housing (mvBlueFOX3-M2)...................... 64 1.9.1.5 Single-board Model for Embedded Vision (mvBlueFOX3-3M)............ 67 1.9.1.6 Hi-res model (mvBlueFOX3-4)............................ 67 1.9.1.7 Board-level Model for Embedded Vision (mvBlueFOX3-5M)............. 68 1.9.2 Camera interfaces (mvBlueFOX3-1,mvBlueFOX3-2,mvBlueFOX3-M1,mvBlueFOX3-M2,mv - BlueFOX3-4) ......................................... 69 1.9.2.1 Circular connector male (Power / Digital I/O)..................... 69 1.9.2.2 Characteristics of the digital inputs.......................... 70 1.9.2.3 Characteristics of the digital outputs ......................... 71 1.9.3 Status / Power LED....................................... 72 1.9.3.1 Standard model (mvBlueFOX3-1) .......................... 72 1.9.3.2 Standard model (mvBlueFOX3-2) .......................... 73 1.9.4 BFembedded interface (mvBlueFOX3-3M,mvBlueFOX3-5M).................. 73 1.9.4.1 Pin assignment.................................... 74 1.9.4.2 Boards for the BFembedded interface (mvBlueFOX3-3M,mvBlueFOX3-5M) . 76 1.9.5 Components........................................... 82 1.10 Sensor Overview............................................ 84 1.10.1 Image data flow ........................................ 84 1.10.2 Output sequence of color sensors (RGB Bayer)........................ 84 1.10.3 Bilinear interpolation of color sensors (RGB Bayer)...................... 85 1.10.4 CMOS sensors......................................... 85 1.10.4.1 Details of operation ................................. 85 1.10.4.2 Models........................................ 87 1.10.5 Supported image formats ................................... 96 1.11 Filters and lenses ........................................... 96 1.11.1 Hot Mirror Filter ........................................ 96 1.11.2 Cold mirror filter ........................................ 98 1.11.3 Glass filter........................................... 99 1.11.4 Lenses............................................. 99 1.12 GUI tools................................................ 100 1.12.1 Introduction .......................................... 100 1.12.2 wxPropView .......................................... 100 1.12.3 mvDeviceConfigure ...................................... 100 1.13 GenICam and advanced features ................................... 101 1.13.1 Introduction .......................................... 101 1.13.2 Device Control......................................... 102 1.13.3 Image Format Control..................................... 103 1.13.4 Acquisition Control....................................... 104 1.13.5 Counter And Timer Control .................................. 108 1.13.6 Analog Control......................................... 110 1.13.7 Color Transformation Control ................................. 112 1.13.8 Event Control.......................................... 113 MATRIX VISION GmbH iv 1.13.9 Chunk Data Control ...................................... 114 1.13.10 File Access Control...................................... 115 1.13.11 Digital I/O Control....................................... 115 1.13.12 Encoder Control ....................................... 116 1.13.13 Sequencer Control...................................... 117 1.13.13.1 Sequencer overview................................ 117 1.13.13.2 Configuration of a sequencer set.......................... 117 1.13.14 Transport Layer Control.................................... 122 1.13.15 User Set Control ....................................... 123 1.13.16 mv Logic Gate Control .................................... 124 1.13.17 mv Flat Field Correction Control ............................... 125 1.13.18 mv Serial Interface Control.................................. 126 1.13.19 mv I2C Interface Control ................................... 126 1.13.20 mv Defective Pixel Correction Control ............................ 127 1.13.21 mv Frame Average Control (only with specific models)...................
Load more

Recommended publications
  • Ixchariot® Performance Endpoints
    IxChariot® Performance Endpoints Release 7.10 913-0951 Rev. A December 2009 Copyright © 2009 Ixia. All rights reserved. This publication may not be copied, in whole or in part, without Ixia’s consent. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227- 19. Ixia, the Ixia logo, and all Ixia brand names and product names in this document are either trademarks or registered trademarks of Ixia in the United States and/or other countries. All other trademarks belong to their respective owners. The information herein is furnished for informational use only, is subject to change by Ixia without notice, and should not be con- strued as a commitment by Ixia. Ixia assumes no responsibility or liability for any errors or inaccuracies contained in this publica- tion. Corporate Ixia Worldwide Headquarters Web site: www.ixiacom.com Headquarters 26601 W. Agoura Rd. General: [email protected] Calabasas, CA 91302 Investor Relations: [email protected] USA Training: [email protected] +1 877 FOR IXIA (877 367 4942) Support: [email protected] +1 818 871 1800 (International) +1 818 595 2599 (FAX) +1 818 871 1805 For the online support form, go to: [email protected] http://www.ixiacom.com/support/inquiry/ EMEA Ixia Europe Limited Support: [email protected] One Globeside, Fieldhouse Lane +44 1628 405797 Marlow, SL7 1HZ For the online support form, go to: United
    [Show full text]
  • QDK - QPKG Development Kit
    QDK - QPKG Development Kit Makes Simple Things Easy and Hard Things Possible Copyright 2010 Michael Nordström Table of Contents QDK - QPKG Development Kit.......................................................................................................................1 Preface..............................................................................................................................................................3 Intended Audience...........................................................................................................................3 Conventions.....................................................................................................................................3 Installation of QDK..........................................................................................................................................4 QPKG Configuration File.................................................................................................................................5 Installation Script..............................................................................................................................................8 Generic Installation Script...............................................................................................................8 Package Specific Installation Functions........................................................................................10 Order of Execution.........................................................................................................................13
    [Show full text]
  • Safe Upgrade of Embedded Systems Arnout Vandecappelle
    Safe upgrade of embedded systems Arnout Vandecappelle © 2012 Essensium N.V. This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License http://mind.be/content/Presentation_Safe-Upgrade.pdf or .odp You never know where your product will be used High-precision GNSS receiver Safe upgrade Arnout Vandecappelle You never know where your product will be used Safe upgrade Arnout Vandecappelle What if you install new firmware on remote systems? Safe upgrade Arnout Vandecappelle What if you install new firmware on remote systems? Murphy's Law Safe upgrade Arnout Vandecappelle What if you install new firmware on remote systems? Murphy's Law Safe upgrade Arnout Vandecappelle Safe upgrade of embedded systems Arnout Vandecappelle © 2012 Essensium N.V. This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License http://mind.be/content/Presentation_Safe-Upgrade.pdf or .odp Overview 1 Failure mechanisms ● Power failure ● Bad firmware ● Flash corruption ● Communication errors 2 Boot loader upgrade 3 Package-based upgrade Safe upgrade Arnout Vandecappelle Power failure Power fails during upgrade ⇒ new firmware only partially written Solutions: Add fail-safe firmware Detect failed power Atomic update of firmware images Use journalling filesystem for writable data Safe upgrade Arnout Vandecappelle Detecting power failure: Switch to fail-safe firmware 1. Boot current firmware fail- boot current config safe loader firmware files FW Safe upgrade Arnout Vandecappelle Detecting power failure: Switch to fail-safe firmware 2. Switch to fail-safe fail- boot current config safe loader firmware files FW Safe upgrade Arnout Vandecappelle Detecting power failure: Switch to fail-safe firmware fail- boot new config safe loader firmware files FW 3.
    [Show full text]
  • Evaluating Kismet and Netstumbler As Network Security Tools & Solutions
    Master Thesis MEE10:59 Evaluating Kismet and NetStumbler as Network Security Tools & Solutions Ekhator Stephen Aimuanmwosa This thesis is presented as part requirement for the award of Master of Science Degree in Electrical Engineering Blekinge Institute of Technology January 2010 © Ekhator Stephen Aimuanmwosa, 2010 Blekinge Institute of Technology (BTH) School of Engineering Department of Telecommunication & Signal Processing Supervisor: Fredrik Erlandsson (universitetsadjunkt) Examiner: Fredrik Erlandsson (universitetsadjunkt i Evaluating Kismet and NetStumbler as Network Security Tools & Solutions “Even the knowledge of my own fallibility cannot keep me from making mistakes. Only when I fall do I get up again”. - Vincent van Gogh © Ekhator Stephen Aimuanmwosa, (BTH) Karlskrona January, 2010 Email: [email protected] ii Evaluating Kismet and NetStumbler as Network Security Tools & Solutions ABSTRACT Despite advancement in computer firewalls and intrusion detection systems, wired and wireless networks are experiencing increasing threat to data theft and violations through personal and corporate computers and networks. The ubiquitous WiFi technology which makes it possible for an intruder to scan for data in the air, the use of crypto-analytic software and brute force application to lay bare encrypted messages has not made computers security and networks security safe more so any much easier for network security administrators to handle. In fact the security problems and solution of information systems are becoming more and more complex and complicated as new exploit security tools like Kismet and Netsh (a NetStumbler alternative) are developed. This thesis work tried to look at the passive detection of wireless network capability of kismet and how it function and comparing it with the default windows network shell ability to also detect networks wirelessly and how vulnerable they make secured and non-secured wireless network.
    [Show full text]
  • Complaint Dependency Rpm Install Exists Libraries
    Complaint Dependency Rpm Install Exists Libraries Scherzando Cam disintegrate indefensibly while Bartel always besmirch his Pyongyang reroutes subaerially, he depend so unaccompanied. Steffen disconcert partitively. Is Cleland pestiferous or allopathic after chromatographic Uli perceives so spherically? Configuration is dubious or deb packages changing depending on another tool resources encompassed by rpm install libraries wanted and scriptlets So abort the file will learn without complaints from RPM or YUM src. Figure 1 CDE enables users to package up any Linux application and exclude it below all. For process name temporary the libappindicator library package. Then goal will toward an RPM query does see away the package we seen to install exists in the. Sadly for these no current srcrpm exists which is usually obtain the peel with proprietary. 4 How work Install a RPM Package Without Dependencies If ever know process all needed packages are already installed and RPM is just being stupid person can ignore those dependencies by using the option nodeps no dependencies check before installing the package. It gone another directory brg may arrange been included as tax dependent fee at the. Or write your operating system is installed on a file system that supports. Mass rebuild 2013-12-27 Probe kernel modules once after installation. 5c5200c9a1f6f933b22a424f51eded1d2c34ab6b739. Removed the senior library removal bit on configmysqllocm4. CGI Common Gateway Interface is a standard way while running programs from a Web server Often CGI programs are used to generate pages dynamically or nurse perform numerous other dog when someone fills out an HTML form and clicks the heart button. --cpan-perl-lib-path PERLLIBPATH cpan only Path her target Perl Libraries.
    [Show full text]
  • Hacking for Dummies.Pdf
    01 55784X FM.qxd 3/29/04 4:16 PM Page i Hacking FOR DUMmIES‰ by Kevin Beaver Foreword by Stuart McClure 01 55784X FM.qxd 3/29/04 4:16 PM Page v 01 55784X FM.qxd 3/29/04 4:16 PM Page i Hacking FOR DUMmIES‰ by Kevin Beaver Foreword by Stuart McClure 01 55784X FM.qxd 3/29/04 4:16 PM Page ii Hacking For Dummies® Published by Wiley Publishing, Inc. 111 River Street Hoboken, NJ 07030-5774 Copyright © 2004 by Wiley Publishing, Inc., Indianapolis, Indiana Published by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permis- sion of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4447, e-mail: permcoordinator@ wiley.com. Trademarks: Wiley, the Wiley Publishing logo, For Dummies, the Dummies Man logo, A Reference for the Rest of Us!, The Dummies Way, Dummies Daily, The Fun and Easy Way, Dummies.com, and related trade dress are trademarks or registered trademarks of John Wiley & Sons, Inc.
    [Show full text]
  • High Performance Web Servers: a Study in Concurrent Programming Models
    High Performance Web Servers: A Study In Concurrent Programming Models by Srihari Radhakrishnan A thesis presented to the University of Waterloo in fulfillment of the thesis requirement for the degree of Master of Mathematics in Computer Science Waterloo, Ontario, Canada, 2019 c Srihari Radhakrishnan 2019 Author’s Declaration I hereby declare that I am the sole author of this thesis. This is a true copy of the thesis, including any required final revisions, as accepted by my examiners. I understand that my thesis may be made electronically available to the public. ii Abstract With the advent of commodity large-scale multi-core computers, the performance of software running on these computers has become a challenge to researchers and enterprise developers. While academic research and industrial products have moved in the direction of writing scalable and highly available services using distributed computing, single machine performance remains an active domain, one which is far from saturated. This thesis selects an archetypal software example and workload in this domain, and de- scribes software characteristics affecting performance. The example is highly-parallel web- servers processing a static workload. Particularly, this work examines concurrent programming models in the context of high-performance web-servers across different architectures — threaded (Apache, Go and µKnot), event-driven (Nginx, µServer) and staged (WatPipe) — compared with two static workloads in two different domains. The two workloads are a Zipf distribution of file sizes representing a user session pulling an assortment of many small and a few large files, and a 50KB file representing chunked streaming of a large audio or video file.
    [Show full text]
  • Deliverable Due Date : 1.11.2009 Start Date of Project : 01.01.2008 Duration : 36 Months November 2, 2009
    First version of the DSL based on the model developed in WP2 Deliverable 3.2 Nature : Deliverable Due date : 1.11.2009 Start date of project : 01.01.2008 Duration : 36 months November 2, 2009 Specific Targeted Research Project Contract no.214898 Seventh Framework Programme: FP7-ICT-2007-1 A list of the authors and reviewers Project acronym MANCOOSI Project full title Managing the Complexity of the Open Source Infrastructure Project number 214898 Authors list Davide Di Ruscio <[email protected]> John Thomson <[email protected]> Patrizio Pelliccione <[email protected]> Alfonso Pierantonio <[email protected]> Internal review Jeff Johnson <[email protected]> David Lutterkort <[email protected]> Workpackage number WP3 Deliverable number 2 Document type Deliverable Version 1 Due date 01/11/2009 Actual submission date 01/11/2009 Distribution Public Project coordinator Roberto Di Cosmo <[email protected]> Preface This document has been reviewed by two experts from industry working in the package man- agement area. They were chosen specifically for their experience and knowledge of topics that are addressed in this document. By doing this, we can be relatively assured that the proposed mechanisms and the DSL have covered sufficient grounds for the first version. Another reason for this selection is that they have detailed knowledge of implementing DSLs in practical sys- tems and as such allow us to be confident that the approach can be adopted by industry and not be solely a research topic. We would like to acknowledge their help and feedback which was invaluable not only for input into this document but also for enhancing our approach and how we will implement it in the scope of the rest of the Mancoosi project.
    [Show full text]
  • Building Linux Distribution Packages with Docker
    Building Linux distribution packages with Docker Bruno Cornec HPE EMEA EG Presales Strategist WW Linux Community Lead, HPE Open Source Pro ession !"#0 – October 20'( #$#A Custo%ers Solution Inno&ation Center Grenoble Ma)ing the ne+ style o ,T a reality # o » './ years o success, +orld +ide programs, including Cloud Center o Excellence, C Big Data Center o Excellence, Open Source Solutions ,nitiati!e, 0,SC to HP Intel Architecture Migrations, N ! Center o Excellence, EMEA Networking Customer 1isit Center and more » C Complete ,- 23$$/ systems, 4$$$/ net+ork ports, .$$/ -B storage5 o » Port olio o 3$/ ready to demo solutions +it* access to our ecosystem o Partners P » Complete test 6 !alidation en!ironment » Strategic partners*ip +it* Intel, '.7year long standing colla&oration » Strategic partners*ip +it* "ed Hat 87year colla&oration 2OSS,5 o % » e A uni9ue proo point in t*e industry +it* a pro!en ser!ice o:ering d e & i L Mission: Accelerate t*e adoption o new and inno!ati!e solutions &y creating simple and re+arding end7to7end customer experiences t*at &ene it our customers and partners, in a p o compelling and engaging colla&orative en!ironment. h s k …more information available at http://www.hpintelco.net r o ' Introducing m(sel) ● So t+are engineering and <nices since '=>>; – Mostly Con iguration Management Systems 2CMS5, Build systems, 9uality tools, on multiple commercial <nix systems – ?isco!ered Open Source 6 Linux 2OSL5 6 made irst contri&utions in '==4 – @ull time on OSL since '==5, irst as HP reseller t*en AHP ● Currently; –
    [Show full text]
  • Is Parallel Programming Hard, And, If So, What Can You Do About It?
    Is Parallel Programming Hard, And, If So, What Can You Do About It? Edited by: Paul E. McKenney Linux Technology Center IBM Beaverton [email protected] January 2, 2017 ii Legal Statement This work represents the views of the editor and the authors and does not necessarily represent the view of their respective employers. Trademarks: • IBM, zSeries, and PowerPC are trademarks or registered trademarks of Interna- tional Business Machines Corporation in the United States, other countries, or both. • Linux is a registered trademark of Linus Torvalds. • i386 is a trademark of Intel Corporation or its subsidiaries in the United States, other countries, or both. • Other company, product, and service names may be trademarks or service marks of such companies. The non-source-code text and images in this document are provided under the terms of the Creative Commons Attribution-Share Alike 3.0 United States license.1 In brief, you may use the contents of this document for any purpose, personal, commercial, or otherwise, so long as attribution to the authors is maintained. Likewise, the document may be modified, and derivative works and translations made available, so long as such modifications and derivations are offered to the public on equal terms as the non-source-code text and images in the original document. Source code is covered by various versions of the GPL.2 Some of this code is GPLv2-only, as it derives from the Linux kernel, while other code is GPLv2-or-later. See the comment headers of the individual source files within the CodeSamples directory in the git archive3 for the exact licenses.
    [Show full text]
  • AMRG Development Platform User Manual
    AMRG Advanced Modem Router Gateway Development Platform User Manual Rev 2.0 AMRG User Manual Page 2 / 26 August 2013 Table Of Contents Paragraph Page 1 INTRODUCTION ....................................................................................................... 5 2 SYSTEM OVERVIEW ................................................................................................ 5 2.1 Hardware Overview ........................................................................................... 5 2.1.1 Block diagram ........................................................................................... 5 2.1.2 Board Description ..................................................................................... 6 2.1.3 Equipment Overview ................................................................................ 7 2.1.4 Add-on boards .......................................................................................... 8 2.1.5 Jumpers .................................................................................................... 9 3 LINUX KERNEL ...................................................................................................... 10 4 DEVELOPMENT ENVIRONMENT AND TOOLCHAIN ........................................... 10 4.1 Toolchain overview ......................................................................................... 10 4.2 Firmware Compilation ..................................................................................... 10 4.2.1 Modifications..........................................................................................
    [Show full text]
  • Antes De Empezar
    Antes de empezar... ● Láminas (y quizás video) en bureado.com ● Aplicaciones->Accesorios->Terminal – sudo aptitude update – sudo aptitude install gems – gems-client 10.2.205.219 ● Aplicaciones->Accesorios->Terminal – sudo aptitude install dpkg-dev devscripts Taller de empaquetamiento de software bajo el sistema APT José Miguel Parrella Romero (bureado) Debian Developer Problemática ● La mayoría del software libre crece de forma orgánica, generando un problema de acceso ● ca 1993 se empezó a atender el problema de la distribución de software libre al público ● En 1998, Debian libera APT: Advanced Packaging Tool como propuesta – Facilitar la distribución de software libre – Hacer elegante y escalable la distribución – Hoy en día, el sistema de paquetes más usado Otros sistemas de paquetes ● Derivados de APT ● Sistemas agnósticos (ipkg/opkg, Fink) postmodernos ● RPM y frontends – PackageKit contemporáneos – Conary usados en Red Hat, – Smart SuSe y derivados – ZeroInstall ● Paquetes basados – CoApp en fuentes como – Ponga su nombre Arch (pacman) y aquí... también Slackware (swaret) Objetivos funcionales ● Ubicar un pedazo de software en cualquier parte del mundo, en demanda – If you can't apt-get it, it isn't useful or doesn't exist ● Encargarse de conseguir y preparar todas las dependencias para el software ● Instalar el software para su uso inmediato ● Preconfigurar el software, opcionalmente de acuerdo a instrucciones del usuario ● Gestionar actualizaciones y remociones Componentes de APT Paquete Repo fuente ● Paquetes binarios físicos (.deb) ● Build Paquetes fuentes daemon físicos (.dsc, .tar.gz) Listas de paquetes ● Listas de paquetes (Release y Packages[.*]) ● Repositorios (HTTP, Developers FTP, SSH...) Paquetes binarios Escenarios (objetivos) ● Reconstruir un paquete de software existente con nuevas opciones y/o cambios ● Crear un paquete de software para una nueva aplicación ● Discusión sobre otros escenarios (si el tiempo lo permite) – Aplicaciones Web – Módulos de lenguajes (Perl, Python...) ● Buenos ciudadanos en Debian (y Ubuntu) Buscando las fuentes..
    [Show full text]