Bug#798966: kicad: Packaging of KiCAD 4.0 (currently in RC)

2015-10-12 Thread Jonatas
​The new ​pcbnew kicad modules gets defalts from on-line by github (
https://github.com/KiCad) all dot pretty.

So it have alter in footprint library table to get off line e make a new
pakage "kicad-library-footprint", or put it in the kicad package.


Bug#798966: kicad: Packaging of KiCAD 4.0 (currently in RC)

2015-09-23 Thread Daniel Serpell
Source: kicad
Followup-For: Bug #798966

Hi,

There are packages for Kicad 4.0 rc1 at:
  https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-4

Those seems to build ok in current Debian Sid, so could provide a good
starting point for the Debian packaging.

I'm currently using the binary packages from that PPA and can confirm
that they work.



Bug#798966: kicad: Packaging of KiCAD 4.0 (currently in RC)

2015-09-14 Thread Gregor Riepl
Package: kicad
Severity: wishlist

According to https://lists.launchpad.net/kicad-developers/msg20319.html a new
stable release of KiCAD is imminent, and release candidate work will happen on
https://code.launchpad.net/~stambaughw/kicad/4.0

As far as I can tell, there a number of important changes in respect to the
current Debian kicad packaging files:

- Versioning: It looks like this release will receive a proper version, 4.0,
making the previous date-based version obsolete.
- Documentation and Libraries: Both were previously moved to their separate
projects, but they don't seem to be built/installed as part of the regular
kicad build procedure any more. It may be necessary to write explicit
installation rules or build them as separate packages.
- Plugins: Some components are built both standalone and as plugins that may be
loaded from a different module when needed. These are currently installed as
/usr/bin/_*.kiface - probably not the best place. This should be mentioned to
upstream, so they are placed into /usr/lib/kicad/ or similar instead. Also, the
standalone version of cvpcb is gone. It lives on in plugin form.
- Paths: It looks like it's no longer necessary to patch the template path in
prjconfig.cpp. The code will consult the environment variable KICAD first, then
try to use /../share/kicad/template, and if that isn't found,
fall back to /../share/template.
- Boost: Currently, the build scripts will automatically download boost 1.54
unless -DKICAD_SKIP_BOOST=ON is passed to cmake. I have successfully built
kicad with the boost 1.58 dev packages in Debian, but it may be necessary to
hardcode a certain boost version or rely on the downloaded version instead. A
list of the required sub-packages is attached below.

These are the things I discovered while porting the previous debian/ files to
the new release. I haven't been successful so far, due to the missing doc and
library installation rules, but compilation was successful.

There is currently no installable package for stretch, so I'm a bit desperate
to get kicad 4.0 packaged as soon as possible. Is someone working on
implementing the necessary changes already? If yes, I'll gladly support them
instead.

These are my build dependencies (changes: Boost dependency and minimum cmake
version according to CMakeLists.txt):
Build-Depends: debhelper (>= 9), quilt, libx11-dev,
 libglu1-mesa-dev, libgl1-mesa-dev, mesa-common-dev,
 libwxgtk3.0-dev,
 libboost-dev, libboost-context-dev, libboost-date-time-dev,
 libboost-filesystem-dev, libboost-iostreams-dev,
 libboost-locale-dev, libboost-program-options-dev,
 libboost-regex-dev, libboost-system-dev, libboost-thread-dev,
 cmake (>= 2.8.4), imagemagick



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, armhf

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages kicad depends on:
pn  kicad-common  
ii  libc6 2.19-19
ii  libgcc1   1:5.2.1-16
ii  libgl1-mesa-glx [libgl1]  10.6.5-1
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libstdc++65.2.1-16
pn  libwxbase3.0-0
pn  libwxgtk3.0-0 
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
pn  zlib-bin  

kicad recommends no packages.

Versions of packages kicad suggests:
pn  extra-xdg-menus  
ii  kicad-doc-en 0.20141025+bzr4029-2



Bug#798966: kicad: Packaging of KiCAD 4.0 (currently in RC)

2015-09-14 Thread Gregor Riepl
> - Documentation and Libraries: Both were previously moved to their separate
> projects, but they don't seem to be built/installed as part of the regular
> kicad build procedure any more. It may be necessary to write explicit
> installation rules or build them as separate packages.

I have to correct myself: Branching/exporting the bzr repositories for doc and
libraries into the kicad source directory seems to have actually worked. There
are some problems with certain paths that may need to be addressed, but I do
get a successful and (as far as I can tell) complete build of kicad,
kicad-common and kicad-doc-*.

I'm testing the result now.