Re: [Kicad-developers] Minimum Boost version

ize the number of supported distros whenever possible. fully agreed! Please don't bump versions only because you can do this. Check always if you need some new shiny function that is resulting in a version bump. -- Regards Carsten Schoenert _

Re: [Kicad-developers] Minimum Boost version

Hi, Am 26.09.19 um 22:26 schrieb Ian McInerney: > Ping. Is there any opposition to bumping the minimum Boost version to > 1.59? I still see no technical need to increase the minimal version for Boost. -- Regards Carsten Schoenert ___ Mailin

Re: [Kicad-developers] GitLab migration

point that releases will be on two different places. Please don't do this. As there si no need to do this. Think about a branch model and you will see there is no need to have two different resources to keep the data. -- Regards Carsten Schoenert _

Re: [Kicad-developers] GitLab migration

usually prefer to create the tarball on my machine by the 'git archive' command. But you can also use the plain GitLab API to request a download URL. But that's not really needed as the various download URLs are predictable. -- Regards Carsten Schoenert ___

Re: [Kicad-developers] 5.1.5 release status

ration is visible in the GitLab repo for KiCad on Salsa. https://salsa.debian.org/electronics-team/KiCad/kicad https://salsa.debian.org/electronics-team/KiCad/kicad/blob/debian/sid/debian/rules I'm happily taken any patches if provided. I personally haven't seen these asserts. -- Regard

Re: [Kicad-developers] 5.1.5 release status

ome enlightenment on this? -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Minimum Boost version

ly helpful if upstream maintainer can help. And members of the distro can help regarding planned release time spans for their releases. -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-deve

Re: [Kicad-developers] 5.1.5 release status

. thanks, I merged your PR right now. -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More he

[Kicad-developers] Python files still depending on Python2 only due used shebang

'#!/usr/bin/env python' and a compatibility so the scripts can also be used within a Python3 interpreter? KiCad still has some other (indirect) dependencies on Python2 which will also needed to get resolved, but that's another story. -- Regards Carsten Schoenert __

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

#x27;d for potential shebang lines. Looking at the date within the copyright statement let me be quite sure the files wont be Python3 ready. And this is for sure true for mostly all the existing files. -- Regards Carsten Schoenert ___ Mailing list: h

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

eeded. -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Update python defaults

Am 26.10.19 um 23:03 schrieb Steven A. Falco: I've been building for Fedora using both KICAD_SCRIPTING_PYTHON3=ON and KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON for quite a while now, FWIW. The same is true for Debian builds of KiCad in unstable/testing and buster/buster-backports for a while (since 5.

Re: [Kicad-developers] Building Kicad on Windows 10/Eclipse/Msys2

ed one ore more remotes. If you have only one remote configured git tries to be smart and is substitute the rest for the command by the obviously logical value. So, if you want to be safe than the full command line is correct. -- Regards Carsten Schoenert __

Re: [Kicad-developers] Linux Packagers: Resource File Updates

screenshots should be updated too. ;) The validator for the AppData content within the Debian QA is mentioning that the component ID is not a reverse domain-name. Should get fixed too in case the file is getting changed. > https://appstream.debian.org/sid/main/issues/kicad.html -- Regards Carste

Re: [Kicad-developers] Linux Packagers: Resource File Updates

age and install the data into a temporary folder from which the package(s) are created. So the final appdata file needs to be installed into this temporary folder, but that's already happen now. -- Regards Carsten Schoenert ___ Mailing list: http

Re: [Kicad-developers] Linux Packagers: Resource File Updates

k a size of 1024x576 is fine, but a greater size would also be o.k. The images should help users to get an overview of the application, so a bigger screenshot would be better than a smaller one. -- Regards Carsten Schoenert ___ Mailing list: http

Re: [Kicad-developers] FOSDEM 2020

website please so all is visible easily? -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] FOSDEM 2020

x27;s not needed. I'm mostly interested in the basic headlines like where to find the devroom etc. -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net U

[Kicad-developers] Inconsistency within l10n strings

ost of the variables are inside double quotes. Wouldn't it make sense to write up all these strings based on the same rules? -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists

Re: [Kicad-developers] Inconsistency within l10n strings

too, but every time the original string is changed I need to review this again. But the English source itself should be consistent on this to lower down the work on currently 5.722! strings. :-) -- Regards Carsten Schoenert ___ Mailing list: http

Re: [Kicad-developers] Please be kind towards translators

altium2kicadpcb_plugin/altium_pcb.cpp: > wxString::Format( _( "No text position present for leader dimension object" ) > ) ); For the latter I'm not sure, but wxLogError looks not like it's some string for the UI. Nitpick, it's not a sentence, the leading

Re: [Kicad-developers] Please be kind towards translators

And as we are on 'wxString errmsg', plugins/pluginldr.cpp is containing a lot of strings like > wxString errmsg = _( "missing function 'GetVersion'" ); Looks to me as these are also no strings for the normal user. Or am I wrong her

Re: [Kicad-developers] Is it really the case that installing KiCad on a Mac requires manually copying files around?

ied can make some bigger damage on a project than the broader "normal" audience. So try to keep this one group of people, that you will never serve completely, always small as possible. -- Regards Carsten Schoenert ___ Mailing list:

[Kicad-developers] Broken default fp-lib-table, removed footprint library

an increased *micro* version! People do not expect such changes. And the majority of user isn't following the development of KiCad itself or the libraries in deep! Keep that in mind please. Thanks. -- Regards Carsten Schoenert ___ Mailing

Re: [Kicad-developers] no broken default fp-lib-table, removed footprint library

would get communicated in a better way. The simplest thing is a text file within the repository, mostly called README. :) I haven't found any information in the git tree, in the mailing list, on the KiCad website or on GitHub. -- Regards Carsten Schoenert ___

Re: [Kicad-developers] no broken default fp-lib-table, removed footprint library

the users POV and how they expected thing to behave. The gap between the software developers and the users is filled by the packages user install and use. But the packagers are completely depending on the information they have and can get from the developers. And here for KiCad these people sit

Re: [Kicad-developers] no broken default fp-lib-table, removed footprint library

Hello Wayne, Am 14.05.20 um 18:43 schrieb Wayne Stambaugh: Carsten, What information do you need from KiCad. Does Debian (or any other disto) have recommendations for upstream projects to help packagers? Debian has some dedicated information for upstream projects and coders of course. htt

Re: [Kicad-developers] New Build Dependencies: Lemon + GTK3

Hello Ian, Am 03.08.20 um 19:39 schrieb Ian McInerney: I have now updated this so that we bundle the lemon parser code inside thirdparty and build it for ourselves (it is only 1 main c file that was released into the public domain). CMake then takes care of all the pathing for the template and

Re: [Kicad-developers] New Build Dependencies: Lemon + GTK3

Mark, Am 03.08.20 um 20:19 schrieb Mark Roszko: But this is also a nightmare. I don't know what you mean here. 1. The main issue is the tool is not a real independent tool, it is only maintained within sqlite and everyone using it outside of that are "welcome to" by sqlite but the global li

Re: [Kicad-developers] New Build Dependencies: Lemon + GTK3

Am 03.08.20 um 20:42 schrieb Steven A. Falco: What is the resolution? Do I undo the dependency on the lemon parser generator? Or will there be a flag to select whether to generate or use the canned one? In my eyes there is only one solution. Always prefer a dependency as external required de

Re: [Kicad-developers] 5.1.9 tagged for release

Hi, Am 22.12.20 um 23:01 schrieb Nick Østergaard: > I don't think we need that long. Everything seems to be tagged. I have > triggered the windows build and it should just be a simple pkgver bump > for macos and ubuntu ppa as well. please do also remember that there is more out there than the bui

Re: [Kicad-developers] 5.1.9 tagged for release

Hell Nick, Am 23.12.20 um 10:07 schrieb Nick Østergaard: > Hi Carsten > > This is a balancing act. Quite some time ago we decided that we should > make the release _announcement_ (on the website) when we have build > available for some major platforms, these specifically being windows, > ubuntu p

[Kicad-developers] Build problem of current master tree

Hi, since a long time I'm trying to build a current version of 5.99 again. But my attempt is failing with this error. > [ 70%] Built target eeschema_kiface_objects > Scanning dependencies of target eeschema_kiface > [ 70%] Building CXX object > eeschema/CMakeFiles/eeschema_kiface.dir/eeschema.cp

Re: [Kicad-developers] Build problem of current master tree

Hello Jeff, Am 02.01.21 um 15:45 schrieb Jeff Young: > Hi Carsten, > > Known problem when building 5.99 in a tree that used to hold 5.1. > > Try: > > cd include > rm *_lexer.h ahh, yes that fixed the build. But I see the build of additional required files within the source tree rather as issue

Re: [Kicad-developers] Build problem of current master tree

Hello Seth, Am 02.01.21 um 17:02 schrieb Seth Hillbrand: > Hello Carsten- > > We agree with you.  This is why we moved the generated files to the > build tree and out of the source tree.  But legacy files in the source > tree are still considered first, so older build directories need the > fix-u

Re: [Kicad-developers] Build problem of current master tree

Hi, Am 02.01.21 um 17:17 schrieb jp charras: > > Le 02/01/2021 à 17:09, Nick Østergaard a écrit : >> FYI, there are still generated files in the source which are also >> checked in to the source tree: >> >> After a make clean: >> deleted:    ../eeschema/dialogs/dialog_bom_help_md.h >> deleted:  

Re: [Kicad-developers] Build problem of current master tree

Am 02.01.21 um 18:07 schrieb jp charras: > What is the problem with these files? They are build in tree in case you do a configure out of tree? > They are already the final header files built from the corresponding .md > files. In my eyes it's simply the wrong way to build files in another plac

Re: [Kicad-developers] ngspice-34

Hello, Am 02.02.21 um 22:07 schrieb Jean-Samuel Reynaud: > FYI: > As I see the PATH for the file ngspice/config.h is changed on > ngspice-34. And on debian package this file is no more distributed on > this version (as I see on last updated package). > > So there is an impact on some KiCad code:

Re: [Kicad-developers] ngspice-34

Am 03.02.21 um 08:34 schrieb Holger Vogt: > To obtain version information of the currently available libngspice-0.so > version, you might do the following: > > load libngspice-0 dynamically > initialze libngspice > send the command 'version -s' > retrieve some text response similar to the followi

Re: [Kicad-developers] ngspice-34

Hello Holger, Am 03.02.21 um 11:20 schrieb Holger Vogt: > > I remember some time ago I tried to address the libtool versioning, but > I did not understand it, so abandoned it again. libtool isn't really easy, yes, but the more complicated thing is to integrate the things correctly into configur

Re: [Kicad-developers] ngspice-34

Am 03.02.21 um 13:03 schrieb jp charras: > OTOH, a version.h file is not a bad idea (read: for me a very good idea): > > at least the name is already a useful comment and it request only a very > few amount of work. > > Many tools use this trick (for instance opencascade, and most of other > to

[Kicad-developers] possible license mismatch in bitmaps_png/sources ?

Hi, while working on a current snapshot (42c6af4) of the KiCad development tree and adjusting the build environment for Debian unstable I'm facing the output of the Lintian QS tool about the usage of the non-free Creative Commons Non-Commercial Share-Alike (CC-NC-SA) license for some source files.

Re: [Kicad-developers] possible license mismatch in bitmaps_png/sources ?

Hell Seth, Am 02.04.21 um 17:14 schrieb Seth Hillbrand: > The correct license is CC-BY-SA.  We'll update the SVG to the correct > license. thanks, I'll use some more recent snapshot then as this makes my life easier. -- Regards Carsten ___ Mailing lis

[Kicad-developers] For those wondering about KiCad version 5.99.0 in Debian unstable...

it's not really a version 5.99.0. I made a mistake last week while preparing a current snapshot of all relevant KiCad parts and the kicad package was of course intended for uploading to the distribution experimental but was pushed into unstable/sid due stupidity of me. To fix this error I needed

Re: [Kicad-developers] OCE vs. OCC default build flag

Hi, I can just speak for Debian. Am 17.05.21 um 14:53 schrieb Eeli Kaikkonen: > As far as I can tell, Ubuntu and all derivatives, Fedora, openSUSE, > Debian (if I remember correctly), Arch and Manjaro already use OCC so > that the latest available KiCad 5.99 (and even 5.1) packages for the > late

Re: [Kicad-developers] OCE vs. OCC default build flag

Hi, Am 18.05.21 um 17:01 schrieb Kevin Cozens: > How will this affect those of us who build KiCad from source? I have liboce > packages installed which provide OCE. If you change to OCC what package(s) > will I need then? The distro I use (Linux Mint) has libocct (Open CASCADE > Technology) pac

Re: [Kicad-developers] asciidoc

Hi, this topic more relevant for kicad-doc I think. Am 30.05.21 um 20:34 schrieb Jon Evans: > You want this one: https://github.com/Mogztter/asciidoctor-web-pdf > > On Ubuntu I install it with "sudo npm i -g @asciidoctor/core asciidoctor-pdf" For Debian (and also for Ubuntu) this isn't possible

Re: [Kicad-developers] Experience compiling latest HEAD

Hello Ruth, Am 28.06.21 um 21:34 schrieb Ruth Ivimey-Cook: > I would *really* appreciate an ubuntu "official" nightly build of 5.99 > that uses wx3.1 there was never and probably will never be any official Ubuntu KiCad packages. The "official Ubuntu" packages are taken from Debian by the au

Re: [Kicad-developers] For those wondering about KiCad version 5.99.0 in Debian unstable...

Hello Jon, Am 06.07.21 um 21:45 schrieb Jon Evans: > Hi Carsten, > > I was reminded of this thread because of this forum post: > https://forum.kicad.info/t/how-install-kicad-6-x-on-debian/30034/4 > > Is the fact that there is a 6.0.0 tag on experimental also related to > this issue with versioni

Re: [Kicad-developers] old ngspice in 599 macOS nightly

Hello Holger, Am 22.07.21 um 21:17 schrieb Holger Vogt: > With ngspice-35, there will be to changes concerning the > sharedspice.h API header. > > There is now a preprocessor flag definition added > #define NGSPICE_PACKAGE_VERSION "35" this means too there is now a proper versioned library built?

Re: [Kicad-developers] old ngspice in 599 macOS nightly

Hello Holger, Am 24.07.21 um 14:51 schrieb Holger Vogt: > Carsten, > > library versioning: not yet. > > Did some experiments with libtool library versioning. > The input 0:1:0 (code change but no api change) created a > libngspice.so.0.0.1. that's correct, just increase the revision (or age if

Re: [Kicad-developers] libngspice versioning by libtool

Hello Holger, Am 27.07.21 um 14:03 schrieb Holger Vogt: > So what would be the correct action? > > When I compile ngspice, I get (besides libngspice.so.0.0.0 or > libngspice.so.0.0.1) two aliases libngspice.so.0 and libngspice.so. What > would be the correct version to link to? there is nothin

Re: [Kicad-developers] libngspice versioning by libtool

Am 27.07.21 um 20:12 schrieb Holger Vogt: > Carsten, > > it is not about what I should do, but what the KiCad devs should do to > allow me adding versioning to shared ngspice. I will add versioning if > it is aknowledged by KiCad/Eeschema. That's not the question in my eyes. It's not something

Re: [Kicad-developers] libngspice versioning by libtool

Hi, Am 28.07.21 um 14:14 schrieb Ian McInerney: > Depending on how the OpenSUSE build system si setup, a prebuilt version > from their repository might not work with a library with a different > version. Many build systems for Linux packages will encode a dependency > on a specific version of the

Re: [Kicad-developers] libngspice versioning by libtool

Hi again, Am 29.07.21 um 10:29 schrieb Carsten Schoenert: > From a quick built of ngspice (branch pre-master with current HEAD) I > can run a KiCad 5.99 without issues with a new version of > libngspice0.so.0.0.1. > > Will do further testing this. to shorten the story, I can u

Re: [Kicad-developers] libngspice versioning by libtool

Am 30.07.21 um 14:53 schrieb Holger Vogt: [snip] > Ah, and what is the versioning now? The API has not changed, it was > however not described correctly in sharedspice.h, which now (ngspice-35) > will be fixed. So you have changed the internal behavior of one or more symbols? This is of course

Re: [Kicad-developers] libngspice versioning by libtool

Hi Holger, Am 31.07.21 um 15:52 schrieb Holger Vogt: > Hello Carsten, > > there are two thing now open: > > I have made an update to ngspice in branch pre-master: > Now all boolean symbols transferred over the ABI are of true boolean > type. So the interfacing from any caller does not need to b

Re: [Kicad-developers] libngspice versioning by libtool

Am 02.08.21 um 13:11 schrieb Ian McInerney: > This error has been discussed on the list before, but basically it is > caused by using the same source tree and trying to build both 5.1 and > master by switching back and forth between them using git checkout. > There were several changes to where au

Re: [Kicad-developers] 5.1.11 release tagged

Hello Wayne, Am 26.10.21 um 13:32 schrieb Wayne Stambaugh: I just pushed the 5.1.11 tag to the 5.1 branch so please tag all of the other repos so we can start the packaging process. Please let me know if there are any issues that would delay the tagging. I guess the loss of kicad-pcb.org isn'

Re: [Kicad-developers] 5.1.11 release tagged

Hello Wayne, Am 26.10.21 um 20:38 schrieb Wayne Stambaugh: > Hi Carsten, > > Do we still we still build and deploy the old 5.1 developer docs > anywhere? I guess I should remove them just in case someone else does. > I should be able to get to this shortly. stuff from that folder isn't goin

Re: [Kicad-developers] Note to packagers: new data dependency for KiCad PCM

Hello Jon, Am 08.11.21 um 03:30 schrieb Jon Evans: > Hi all, > > We just turned the plugin and content manager (PCM) feature on for all > users. > > To work properly, this feature needs an additional directory packaged: > > $KICAD_DATA/schemas > > If your packaging scripts already grab everyth

Re: [Kicad-developers] V6 documentation

Hello, Am 19.01.22 um 17:21 schrieb Gabriel Staples, ElectricRCAircraftGuy.com: ... In other words, please do make "online documentation" only, as it allows faster updates to it and better consistency, please don't! It absolutely doesn't hurt to build completely offline usable documentation.

Re: [Kicad-developers] V6 documentation

Hello Jon, Am 19.01.22 um 17:38 schrieb Jon Evans: Carsten, There is no reason to remove the ability to package docs offline, I just don't think it should be a focus of the project. here start to disagree. In my eyes the offline bundled and created documentation IS a strong service the proj

Re: [Kicad-developers] V6 documentation

Am 19.01.22 um 18:12 schrieb Steven A. Falco: I don't disagree, but really, we could say that everything is always outdated - the code, the libs etc. I have to pick a point in time, and create packages as of that point - currently that point is when a new release is tagged. I.e., it is a manua

Re: [Kicad-developers] V6 documentation

[ I'm on this list, no need to address me dedicated. ] Am 19.01.22 um 18:45 schrieb Jon Evans: I think you misunderstand.  We currently have three rolling releases on docs.kicad.org : V5, V6, and master (nightly). We will continue adding new "rolling release" builds for e

Re: [Kicad-developers] V6 documentation

Hi, Am 19.01.22 um 23:18 schrieb Eeli Kaikkonen: I don't understand why this discussion is so difficult to understand. sorry but I don't understand what problem you are trying to solve! There is no problem within the Linux world and their distros to provide packaged documentation, there is n

Re: [Kicad-developers] Packaging question

ased distros (like Arch) are fundamentally different to major version releasing distros and lower done the requirements on the underlying package manager. To make it short, I assume it's impossible to let every distro have the same packages with t

[Kicad-developers] KiCad 5 RC1 fails to build on mips, powerpc and ppc64el due undeclared initializer LIBCONTEXT_CALL_CONVENTION

e me an advise please as using a porterbox is always a bit of extra work and will of course also need extra free time (I'm currently lacking of course). Thanks! PS: The build issue on armel is probably related to a missing '-mfpu=vfp -msoft-float' option or similar, I will try to reprodu

Re: [Kicad-developers] KiCad 5 RC1 fails to build on mips, powerpc and ppc64el due undeclared initializer LIBCONTEXT_CALL_CONVENTION

Am 09.03.2018 um 07:45 schrieb Carsten Schoenert: ... > I can try to fix this on a Debian porter box but I've no clues if it is > enough to simply add more define lines like the existing ones. Can > someone of the more experienced devs give me an advise please as using a > port

Re: [Kicad-developers] KiCad 5 RC1 fails to build on armel (mips, powerpc and ppc64el due undeclared initializer LIBCONTEXT_CALL_CONVENTION)

Hi up there, a small update for the issue on armel (armvt4, armvt5t). Am 09.03.2018 um 07:45 schrieb Carsten Schoenert: > PS: The build issue on armel is probably related to a missing '-mfpu=vfp > -msoft-float' option or similar, I will try to reproduce this on one of >

Re: [Kicad-developers] Why do current nightlies report that they are kicad 5.0.0-rc2?

ow additional tag -rc2-dev makes it more difficult for distributions to determine if a new version is available. -rc2* is greater as -rc1 and I'd need to tune the watch file again in Debian we use (and it's already a bit more complicated due the dfsg + rc part). The added tag -rc2

[Kicad-developers] Missing translation macros in common/dialog_about/AboutDialog_main.cpp ?

<< _( "Bug tracker" ) < > 149 << ""; // bold & underlined font caption Is this somehow intended that these needed macros are removed in the file common/dialog_about/AboutDialog_main.cpp? Are there any more files to look at

Re: [Kicad-developers] Missing translation macros in common/dialog_about/AboutDialog_main.cpp ?

Am 17.03.2018 um 20:21 schrieb Carsten Schoenert: > Is this somehow intended that these needed macros are removed in the > file common/dialog_about/AboutDialog_main.cpp? > Are there any more files to look at? > > Btw: The hyperlink to the libraries needs too be reworked too. I

[Kicad-developers] MeetUp of KiCad Developers, Librarians and Contributers on MiniDebConf in Hamburg?

Contributers on MiniDebConf in Hamburg? -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://hel

Re: [Kicad-developers] MeetUp of KiCad Developers, Librarians and Contributers on MiniDebConf in Hamburg?

side would help also potential users of KiCad. I'd really like to meet up some experienced library symbol maintainers! This would be more productive than any ML or GitHub conversation for all participants. -- Regards Carsten Schoenert ___ Mailing

Re: [Kicad-developers] Lib maintainers request help for reviewing installation script changes

o solve two different problems and isn't a atomic PR by this. -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~k

Re: [Kicad-developers] rc2

tes a few days for reworking the strings after the rc2 tagging of the KiCad source. I'm terrible low on free time for this right now and mostly need a weekend to do some work. Thanks! -- Regards Carsten Schoenert ___ Mailing list: https://launch

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Am 07.04.18 um 17:34 schrieb Strontium: > Attached is a patch for discussion only. > > Its the minimum change I could come up with to implement a unique > version specific config directory. > > Nick mentioned changing XDG_CONFIG_HOME, that will not work on Windows > or Mac. > And on Linux, etc

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

nds. updates-alternatives has a different approach as you think. It's not designated for this solution you think off. http://williamdemeo.github.io/linux/update-alternatives.html -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Am 12.04.18 um 17:18 schrieb Reece R. Pollack: > The KiCad 4.0.7 Debian Linux package installs files in these directories: > > /etc/profile.d > /usr/bin > /usr/lib/kicad > /usr/lib/python2.7/dist-packages > /usr/share/applications > /usr/share/doc > /usr/share/icons > /usr/share/kicad > /usr/share

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

Am 12.04.18 um 18:33 schrieb Reece R. Pollack: > Yes, I'm going a bit off the original topic. Maybe we should start a new > thread. But I see an issue arising in the future where people are going > to want to install V5 but not give up V4 quite yet. For example, board > houses that accept KiCad

Re: [Kicad-developers] XDG_CONFIG_HOME on all platforms

d also then remove the redundant of processing XDG_CONFIG_HOME. Also true, I already tried to say the same on 8 Apr 2018. https://lists.launchpad.net/kicad-developers/msg35345.html -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~ki

Re: [Kicad-developers] A reminder on Git commit comments

lly on their machine before doing ping pong with pull or merge request. Don't get me wrong, it's awesome what the libraries have been evolved over the last year. It's just a never ending task as you will find always new advantages to get things improved. -- Regards Carsten Schoenert

Re: [Kicad-developers] A reminder on Git commit comments

get there. And that will be a problem in the future I think. You need to document what are the needed steps to get a reproducible outcome. If not all the tedious work of reviewing the pull requests will be on to few people. I've lost the energy and interest to contribute anything because o

Re: [Kicad-developers] Initial rc6 development.

he freeze for the packages is in January 2019, this isn't that far away from now. My personal impression is that we will still have GTK2+ related packages in Buster. The current stable release Stretch isn't a problem as the packages and versions are frozen. -- Regards Carsten Sc

Re: [Kicad-developers] Initial rc6 development.

g into the issue I posted the current problem on kicad-doc-devs. I appreciate any help to solve the current build issue. https://lists.launchpad.net/kicad-doc-devs/msg00128.html -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kica

Re: [Kicad-developers] rc2 tagged

eciation for all that you do to make KiCad possible. excellent! But I can't find the related tag 5.0.0-rc2 in both git trees, not on Launchpad nor on GitHub. Forgotten to push the tags also? https://git.launchpad.net/kicad/refs/tags https://github.com/KiCad/kicad-source-mirror/tags --

Re: [Kicad-developers] rc2 tagged

Hello Wayne, Am 21.05.18 um 13:55 schrieb Wayne Stambaugh: >> excellent! >> But I can't find the related tag 5.0.0-rc2 in both git trees, not on >> Launchpad nor on GitHub. Forgotten to push the tags also? > > Ahh! I forgot to push the tags. I have it tagged on my system at home. > I will push

Re: [Kicad-developers] rc2 tagged

Hi Wayne, Am 22.05.18 um 23:06 schrieb Wayne Stambaugh: > I forgot to push my tags last night. I just did it so you should be > able to clone from rc2 now. I would rather not move the rc2 tag commit > because I would have to move the KiCadVersion.cmake file changes and > overwrite the repo be

Re: [Kicad-developers] partially untranslated strings in simulation dialog

is for sure just a oversight by the developers and not a intended behavior. I'd hereby suggesting you prepare a patch about such strings. I've seen this also from time to time but didn't get backed out a patch yet due time limitations. -- Regards Carsten Schoenert

[Kicad-developers] KiCad 5.0.0~rc2 now available in Debian experimental

y. -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad 5.0.0~rc2 now available in Debian experimental

s exactly about this. https://salsa.debian.org/electronics-team/KiCad/kicad/blob/debian/sid/debian/rules#L40 -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Un

[Kicad-developers] Making adding of additional symbol *-sym-table files more easy and user friendly?

Hi, the following is clearly something about which hasn't a priority for the current 5.0.0 finalization work. I was thinking about also packaging the digikey-kicad-library [1] for Debian. This is more an easy task so basically I've got a running package which I can use in KiCad. But ... the inte

Re: [Kicad-developers] Making adding of additional symbol *-sym-table files more easy and user friendly?

able? More or less also true. In the end the editors should be smart enough to get a knowledge about were the libraries are laying around once they are found in the root of the default or the local config folders. -- Regards Carsten Schoenert ___ Mailing l

Re: [Kicad-developers] python plugin folder misplaced?

Python specific folder. And also binary based plugins need to go to a folder which is respecting the rules of the LSB. -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpa

Re: [Kicad-developers] Can the -rc tar be made available on launchpad?

Am 01.06.18 um 21:18 schrieb Steven A. Falco: I am starting to look at packaging KiCad 5.0.0 for Fedora. I can download source tars from the 4.X series using URLs like: > https://code.launchpad.net/kicad/4.0/4.0.0-rc2/+download/kicad-4.0.0-rc2.tar.xz However, if I try this with 5.0, I get an er

Re: [Kicad-developers] Can the -rc tar be made available on launchpad?

a realistic time window to get recently made changes into their languages. I just used the current states to create the needed tarballs as we are talking about "just" a release candidate and I also need to look at my timetable to get all things together, b

Re: [Kicad-developers] Untranslated strings

e the changes right now instead in one of the point releases after 5.0.0. So from my side a clear go, do it right now. -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.n

Re: [Kicad-developers] ngspice-28 for KiCad

#x27;s usable in unstable or testing later. -- Regards Carsten Schoenert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://he

Re: [Kicad-developers] ngspice-28 for KiCad

ted binaries into the different packages. https://github.com/tijuca/ngspice-dfsg/blob/debian/sid/debian/rules#L59 PS: The three different configure calls are not from me, this was done already by the previous ngspice maintainers in Debian. -- Regards

  1   2   3   >