DOCSLIB.ORG

QDK - QPKG Development Kit

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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 Installation/Upgrade..................................................................................................................13 QDK Variables...............................................................................................................................................15 Build Scripts...................................................................................................................................................19 User Configuration File..................................................................................................................................21 Invoking qbuild..............................................................................................................................................22 Initialize a Build Environment.......................................................................................................22 Control the Build...........................................................................................................................22 Trust but Verify.............................................................................................................................23 Exclude Files..................................................................................................................................23 Scripts............................................................................................................................................23 Status Information..........................................................................................................................23 Sections..........................................................................................................................................24 Extract QPKG Packages................................................................................................................24 Query Packages..............................................................................................................................24 Help and Usage..............................................................................................................................24 Creating a QPKG Package Using QDK..........................................................................................................25 Creating a Simple QPKG Package................................................................................................25 Creating Platform Specific QPKG Packages.................................................................................27 Converting an Existing QPKG Package........................................................................................31 Appendix A – QPKG Format.........................................................................................................................35 Header Script.................................................................................................................................35 Control Files..................................................................................................................................36 Data File.........................................................................................................................................36 Extra Data Files.............................................................................................................................36 QDK Area......................................................................................................................................37 Tail Section....................................................................................................................................37 2 Preface QDK is used to build QPKG packages. A QPKG package is a self-extracting archive with application files and meta-data. A QPKG package makes it easy for anyone to install and remove packages. It also gives a package maintainer almost total control on how the package is installed on the NAS. The major design goal of QDK is to make it easy for the package maintainer to create a QPKG package. QDK started out as a simple modification of the first official release of the QPKG SDK, but now supersedes it. It includes many new features like architecture check at installation, support for digital signatures, different compression algorithms, a comprehensive option to check that other required QPKG packages or Optware packages are installed (or that conflicting packages are not installed), automatic installation of required Optware packages, and a powerful build script. QDK is distributed under the GPL making it completely open and available for anyone to use. Intended Audience This document is about creating QPKG packages. As such, it assumes that the reader already has some previous knowledge about QPKG packages and at least know how to install and enable a QPKG package using the web interface. This document assumes that you have a basic knowledge of common shell commands. It also helps if you have some familiarity with shell scripts. Conventions The following conventions are used in this document. Italic is used to indicate files, directories, commands, and program names when they appear in the body of a paragraph. Constant Width is used in examples to show the contents of files or the output from commands, and to indicate environment variables, keywords, function names, and other code snippets in the body of a paragraph. Constant Bold is used in examples to show input that is typed literally by the user. # is the shell prompt. [ ] surrounds optional elements in a description of program syntax. The brackets themselves should never be typed. ➥ is the code-continuation character that is inserted into code when a line shouldn't be broken, but we ran out of room on the page. 3 Installation of QDK Before we can start using QDK we have to install it. It is distributed as a platform-independent QPKG package and can be installed using the normal web interface. When installed and enabled QDK is ready to be used. At installation a directory structure is created at the default QPKG location, which depends on whether it is installed on a RAID volume or a single drive. The exact location is available in the QDK_PATH variable in the system-wide configuration file, /etc/config/qdk.conf, but it is usually /share/MD0_DATA/.qpkg/QDK on a RAID system and /share/HDA_DATA/.qpkg/QDK on a single drive system. bin/ qbuild scripts/ qinstall.sh template/ arm-x09/ arm-x19/ config/ icons/ shared/init.sh x86/ x86_64/ package_routines qpkg.cfg qdk qdk is the init script used to enable and disable QDK. This script is run automatically when QDK is enabled or disabled in the web interface. It creates and removes a symbolic link to the qbuild application in /usr/bin. qbuild is the build script. qinstall.sh is the part of the installation script that includes the generic installation functions common to all QPKG packages. This file is never edited by the user. All user defined actions are added to a separate file, package_routines. The template directory include files for a new build environment that can be created using qbuild. By default it includes common subdirectories where the content should be placed and templates for the package specific installation functions, package_routines, the QPKG configuration file, qpkg.cfg, and an init-script. The init- script, init.sh, is renamed to the same name as the package when the new build environment is created. There are also four hidden files, .qpkg_icon.gif, .qpkg_icon_80.gif, .qpkg_icon_gray.gif, and .uninstall.sh. The three first files are the default icons used for QDK in the web interface and the last file is the script run to perform the required actions to clean up after QDK when it is removed using the web interface. This file is created automatically for all QDK based packages at installation time. 4 QPKG Configuration File We begin
Load more

Recommended publications
  • On Applicability of Wireless Routers to Deployment of Smart Spaces in Internet of Things Environments Sergey A
    The 9th IEEE International Conference on Intelligent Data Acquisition and Advanced Computing Systems: Technology and Applications 21-23 September 2017, Bucharest, Romania On Applicability of Wireless Routers to Deployment of Smart Spaces in Internet of Things Environments Sergey A. Marchenkov, Dmitry G. Korzun Petrozavodsk State University (PetrSU) Petrozavodsk, Russia fmarchenk, [email protected] Abstract – The use of wireless technologies is now in- to extend the platform architecture with other protocols evitable in smart spaces development for Internet of Things. by adding new modules. Consequently, the use of wired A smart space is created by deploying a Semantic Informa- and wireless TCP/IP networks is inevitable in Smart-M3- tion Broker (SIB) on a host device. This paper examines the applicability of a wireless router for being a SIB host based development of smart spaces. device to deployment of smart spaces in Internet of Things Wi-Fi is the most common wireless technology to environments. CuteSIB is one of SIB implementations of interconnect different IoT-enabled devices. Almost every the Smart-M3 platform and focus is on Qt-based devices. smart space environment is equipped with a wireless We provide a technique for creating an OpenWrt-based embedded system composed of CuteSIB software compo- access point (a wireless router) to ensure interaction nents for a smart spaces deployment using a cross-compiling between SIB and agents that operate on mobile devices method. The resulting embedded system is used to deploy (e.g. smartphones, tablets). In this configuration, SIB is the SmartRoom system—a Smart-M3-based application that deployed on a dedicated host device (e.g.
    [Show full text]
  • TVS-Ecx80+ Edge Cloud Turbo Vnas Series the Best Storage Solution for Edge Cloud Use Your Turbo Vnas As a PC
    TVS-ECx80+ Edge Cloud Turbo vNAS Series The Best Storage Solution for Edge Cloud Use your Turbo vNAS as a PC 1 2 3 Keys to Super Boost 3 System Performance Flagship model 1 2 3 TVS-EC1080+ Intel® Quad-Core Xeon® E3-1245 v3 3.4GHz and 32GB RAM Built-in dual-port 10GbE and 256GB mSATA modules 10GbE Network Adapter DDR3 Memory mSATA Module MAX 32GB 4K 2K RAM • Supports Intel® Quad-Core Xeon® E3-1245 v3 3.4GHz / Intel® Core™ i3 Dual-Core processors integrated with Intel HD Graphics P4600 • Inbuilt two 10GbE ports reaching over 2000 MB/s throughput and 223,000 IOPs • Scale-up storage to 400 TB raw capacity • Powered by QTS 4.1.2 with new HD Station 2.0 for 4K/2K video TＶS-ECx80+ Turbo vNAS Series transcoding and playback • Q’center centralized management system for managing multiple QNAP Turbo vNAS units • Use the NAS as a PC with exclusive QvPC Technology • Designed for file management, backup and disaster recovery TVS-EC1080+-E3 TVS-EC1080-E3 TVS-EC880-E3 • NAS and iSCSI-SAN unified storage solution for server virtualization TVS-EC1080-i3 Hybrid Enterprise Cloud Storage Architecture With the advent of cloud computing, it is inevitable for enterprises to increase their investments in cloud services. However, enterprises are reducing IT expenses to maximize the return on investment (ROI). In addition to controlling rising costs, IT administrators must take many considerations when facilitating cloud environment. They need to incorporate new technology into existing systems without impacting the stability and performance of the system and user experience.
    [Show full text]
  • 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]
  • 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]
  • QNAP TS-X31 Series Datasheet
    New Turbo NAS TS-x31 Series with Dual-core 1.2GHz Processor A Digital Notepad & Multimedia Center on Your Private Cloud TS-x31 Series • Energy efficient Freescale™ ARM Cortex-A9 dual-core 1.2GHz processor • Up to 110 MB/s read and 80 MB/s write speeds • 3 x SuperSpeed USB 3.0 & dual LAN ports* • Supports 802.11ac USB Wi-Fi adapter * Only for TS-231 & TS-431 Dual x 2 SS Core 1.2 SATA Dual USB eSATA GHz 2.5"/3.5" GbE Ports 3.0 x 3 Port TS-131 TS-231 TS-431 Key features • Create personal cloud notes conveniently with mobile app support • Features the intuitive QTS 4 with multi-window & multi-tasking design for easy NAS management and backup center SOHO & HOME • Easily manage, share and access photos, music and videos TS-x12, HS-210 - Marvell 1.6GHz processor - 512MB DDR3 RAM TS-x21 X 2 - Marvell 2.0 GHz processor - 1GB DDR3 RAM days, every family has tons of photos, music, and videos These stored in different places and on different devices. Convenient access to this content to enjoy and share in a variety of ways is increasingly essential in modern homes. The new QNAP Turbo NAS TS-x31 series for home, SOHO and SMB users is powered by an energy-efficient Freescale™ ARM Cortex-A9 dual-core 1.2GHz processor with Floating Point Unit and 512MB DDR3 RAM. Not only does it operate quietly, but it also uses less electricity for reduced operating costs. The TS-x31 series provides volume encryption to ensure the safety of sensitive personal data.
    [Show full text]
  • Package Managment Package Managment
    2021/09/25 17:11 1/3 Package Managment Package Managment The DSM is not shipped with a package management. If you want to add functionality such as 'vim' or 'sudo', then install the 'ipkg' package manager first. This guide was written for DSM 4.3, but it also applies identically to DSM 5.1. ipkg The following bootstrap files need to be run for the different versions of DSM hardware. Check the CPU version if in doubt as root: # cat /proc/cpuinfo Hardware CPU Bootstrap Original Remarks DS3612xs Intel Core i3 CPU Bootstrap-i686 Bootstrap-i686 also applies to DSM 4.3 VMs special original download DS212+ Marvel 6282 CPU Bootstrap-mv6282 Bootstrap-mv6282 instructions Freescale QorIQ DS213+ Bootstrap-p1022 Bootstrap-p1022 see also PowerPC e500 P1022 CPU Copy the file to the DSM or get it directly from the command line, then make it executable and run it. The example below is for the i3 bootstrap, replace the file name accordingly: # wget http://ipkg.nslu2-linux.org/feeds/optware/syno-i686/cross/unstable/syno-i686 -bootstrap_1.2-7_i686.xsh # chmod +x syno-i686-bootstrap_1.2-7_i686.xsh # ./syno-i686-bootstrap_1.2-7_i686.xsh Reboot the VM or NAS. Change the path of your user and root as described in Configuration. To install apps, run the following: ipkg update ipkg install <app> Also refer to Synology CPU Table and Overview on modifying the Synology Server, bootstrap, ipkg etc. Other resources: IPKG FTP Download Mirror Bernard's Wiki - https://wiki.condrau.com/ 2021/09/25 17:11 2/3 Package Managment apps sudo # ipkg install sudo After installation, run visudo and uncomment the line starting with '%sudo' which defines rights for members of the sudo group.
    [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]
  • 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]
  • 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]