"MagicBox" 16 - Codename Horn
Upcoming SlideShare
Loading in...5
×
 

"MagicBox" 16 - Codename Horn

on

  • 997 views

This is the first presentation about the development process of the new Debian/Ubuntu based Caixa Mágica version, codename "Horn"

This is the first presentation about the development process of the new Debian/Ubuntu based Caixa Mágica version, codename "Horn"

Statistics

Views

Total Views
997
Views on SlideShare
843
Embed Views
154

Actions

Likes
0
Downloads
1
Comments
0

5 Embeds 154

http://pinguinsmagicos.blogs.sapo.pt 146
http://www.alphamatrix.org 4
http://corptv.caixamagica.pt 2
http://alphamatrix.info 1
http://spondulix9.ignisi.com 1

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    "MagicBox" 16 - Codename Horn "MagicBox" 16 - Codename Horn Presentation Transcript

    • “ MagicBox” 16 – Codename Horn Development and creation process Flávio Moringa [email_address] - Caixa Mágica Linux distribution project leader
    • 1. Why Debian/Ubuntu based
      • Debian is known as the best “distro” around... in terms of number and quality of packages, security fixes, system wide stability, etc...
      • Debian is “THE” distribution to use for servers and firewalls...
      • Ubuntu is the most well known Desktop distro, finally bringing Linux to the mainstream Desktop arena;
      • Our current base distribution as an uncertain future, so for a change to occur this is the time;
      • Our clients were asking for “Ubuntu”... because that's what they know...
      • Many well known applications first release .deb packages.
    • 1. Automatic syncronization process
      • 1.1 Syncronize Ubuntu Packages with our repository – By Henrique Rocha
      Use apt-mirror to retrieve all latest packages from upstream Filter non magicbox packages Adds non magicbox packages to contribware DB as testing packages Adds non magicbox packages to our working repository http://archive.ubuntu.com/ubuntu http://ftp.caixamagica.pt/magicbox file://home/repoadmin/apt-mirror/ubuntu http://contribware.caixamagica.pt
    • 1. Automatic syncronization process
      • 1.2 Syncronize MagicBox Packages with our repository – By Henrique Rocha
      Use apt-mirror to retrieve all latest packages from upstream Filter magicbox packages reading the SVN listing Adds magicbox packages to contribware DB as packages needing building Adds magicbox packages to our working repository Tries to apply our changes to sources http://archive.ubuntu.com/ubuntu http://ftp.caixamagica.pt/magicbox file://home/repoadmin/apt-mirror/ubuntu http://contribware.caixamagica.pt CMiffy
    • 1. Automatic syncronization process
      • 1.3 Buildbot's building farm – By Pedro Rodrigues
      Packages commited to our svn's source packages trunk dir are Sent to Contribware for compilation using a svn hook script Packages in a state of “Building” are scheduled to be sent to the Buildbot farm for compilation If the build is succefful the resulting packages are added to our repository http://contribware.caixamagica.pt http://contribsoft.caixamagica.pt http://ftp.caixamagica.pt/magicbox Buildbot
    • 2. Software Center – Ratings and reviews
      • Implementing Ubuntu's software center ratings and reviews server using Contribware;
      • Problems:
        • Launchpad heavy integration;
        • Usage of webservices we do not have;
        • Extra info our database model does not have;
        • Authentication to our LDAP directory for posting;
      • Done:
        • Change our database model to allow for reviews and ratings for a package;
        • Webservice to retrieve data, no authentication needed;
      • In progress:
        • Everything else ….
      • Main Developer -> Ricardo Teixeira
    • 3. Changes to Ubuntu
      • Changing every reference to Ubuntu in images, logos, text, etc;
      • Changing the default theme;
      • Changing the default color;
      • Using our new name and logo – To be selected still...
      • Not using Unity by default;
      • Using our own repositories;
      • Making our non-official contributions repository available;
      • Pre-install extra codecs and drivers;
      • Tell us what else...
    • 4. Contribware Changes
      • Contribware source packages upload needs to be changed to allow deb sources to be uploaded;
      • There should be a clear difference between old – RPM – and new – DEB – packages;
      • Due to the database model changes packages should now also show their reviews and ratings if any;
      • Tell us what else...
    • Thank You Thanks for you attention. Feel free to ask me more questions, either in person or through: [email_address]