Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

[packaging] C::B offically in Ubuntu, pending submission to Debian.

(1/3) > >>

Sonic McTails:
I've been working on cleaning up the code::blocks package and correcting it for submission into Ubuntu; a rather large chunk of the rules file needed to be changed, as well as a few other changes for Code::Blocks to meet the Linux Standard Base/Debian/Ubuntu packaging requirements

The biggest change in this regard was the plugins folder has to be moved from /usr/share/codeblocks/plugins to /usr/lib/codeblocks/plugins (share is arch-independent data, and thus actual executable plugins don't belong there; this was the major show stopper for getting the existing deb packages into the archive). I'd ask that the developers make it a seperate configure switch for moving this folder; the current "method" involves a rather nasty hard-coded hack; I'm would be willing to code the changes when I get a chance if the change will be accepted up stream.

Secondly, there appears to be a minor bug with the New Projects window on Xcfe/GNOME (not tested to see if it happens in KDE, but I won't be suprised.). When New > Package is selected, the menu of project templates comes up normally. On Windows, this is a normal list with no icons, and just text, but on Linux, there are spaces for icons, but no actual icons. As this happens both when I built the actual source, and tried the pre-existing debs from this page, I either think this is a bug in wxGTK/wxWidgets, or a bug in C::B; if a dev can please help me to confirm one or the other so it can be resolved ASAP.

TheTuxKeeper:

--- Quote from: Sonic McTails on July 19, 2008, 04:06:55 pm ---The biggest change in this regard was the plugins folder has to be moved from /usr/share/codeblocks/plugins to /usr/lib/codeblocks/plugins (share is arch-independent data, and thus actual executable plugins don't belong there; this was the major show stopper for getting the existing deb packages into the archive). I'd ask that the developers make it a seperate configure switch for moving this folder; the current "method" involves a rather nasty hard-coded hack; I'm would be willing to code the changes when I get a chance if the change will be accepted up stream.

--- End quote ---
I made such a patch/change too: http://forums.codeblocks.org/index.php/topic,8755.0.html :)
you can take a look at it and use it, if you want. i don't know what you call "nasty hard-coded hack", but i wouldn't call my change like this :P
the changes for the debian stuff is missing, i haven't had time to do this.

Sonic McTails:
Oooh, that will help a lot. I'll make sure it goes into the next revision of the package (I need to make some changes into Debian, and then once its in Debian sid, request a sync).
Michael

Jenna:
You can also have a look into "my" debian version, if you are interested.

There are only very less modifications compared to trunk I made in "control" and "rules"-file. (And therefore copyright and changelog of course).

I thought about making C::B really debian and lsb compilant, but i don't have much time in the moment, so it has no priority.

You write that C::B should go in sid. Which version of C::B should there be snapshots of nightlies or a bugfixed-version of 8.02 ?

Sonic McTails:
It's generally preferred that stable release versions go into the archive (there are exceptions like ffmpeg which hasn't had a stable release this decade). C::B would be LSB compliant if the plugins folder was properly moved to /usr/lib/codeblocks/plugins, and any arch dependent code would go there as well.

I'm still trying to figure out what's causing the weirdness with the New Project window though ...

Navigation

[0] Message Index

[#] Next page