Re: [Kicad-developers] V6 documentation

On 1/19/22 05:18 PM, Eeli Kaikkonen wrote: On Wed, Jan 19, 2022 at 9:13 PM Steven A. Falco wrote: It would still be helpful if the doc repo could be tagged at the same point that everything else is tagged, because every single Fedora package needs a correct version in its name. For example,

Re: [Kicad-developers] V6 documentation

On Wed, Jan 19, 2022 at 9:13 PM Steven A. Falco wrote: > It would still be helpful if the doc repo could be tagged at the same point > that everything else is tagged, because every single Fedora package needs a > correct version in its name. For example, it would be very strange (perhaps > "i

Re: [Kicad-developers] V6 documentation

> Here's a wild idea: why not make the documentation bundle(s) downloadable with the PCM? I'm not sure that would be worth the extra effort, since it wouldn't help the people that can't use online documentation because Internet access is restricted. Yes, you could download a PCM package and then

Re: [Kicad-developers] V6 documentation

On Wed, Jan 19, 2022 at 6:38 PM Jon Evans wrote: > > What I would propose to improve the situation is: Here's a wild idea: why not make the documentation bundle(s) downloadable with the PCM? Eeli Kaikkonen ___ Mailing list: https://launchpad.net/~kica

Re: [Kicad-developers] V6 documentation

On 1/19/22 02:16 PM, Jon Evans wrote: On Wed, Jan 19, 2022 at 2:12 PM Steven A. Falco mailto:stevenfa...@gmail.com>> wrote: Not to put words in your mouth, but it sounds like the code will be changed so that when someone clicks on the Help menu, they will get the on-line version, if poss

Re: [Kicad-developers] V6 documentation

On Wed, Jan 19, 2022 at 2:12 PM Steven A. Falco wrote: > > Not to put words in your mouth, but it sounds like the code will be > changed so that when someone clicks on the Help menu, they will get the > on-line version, if possible. > And only if the on-line version cannot be accessed, the code w

Re: [Kicad-developers] V6 documentation

On 1/19/22 12:45 PM, Jon Evans wrote: ... snip ... The point I was making is that someone who installs 6.0.1 today should get the latest V6 branch docs (not the latest master branch) ideally. Anyone with internet access should be able to get the latest docs, not the docs at the 6.0.1 tag. N

[Kicad-developers] V6 documentation

On Wed, Jan 19, 2022 at 1:05 PM Carsten Schoenert wrote: > [ I'm on this list, no need to address me dedicated. ] > My email client does this automatically, but if it bothers you I removed it manually :) > > Am 19.01.22 um 18:45 schrieb Jon Evans: > > > I think you misunderstand. We currently

Re: [Kicad-developers] V6 documentation

About doc, this one seems good but bazaar, no revision, no datestamp ? Is it maintained ? bazaar.launchpad.net/~stambaughw/kicad/doc-read-only/download/head:/1115%4016bec504-3128-0410-b3e8-8e38c2123bca:trunk%252Fkicad-doc%252Fdoc%252Fhelp%252Ffile_formats%252Ffile_formats.pdf/file_formats.pdf

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

On Wed, Jan 19, 2022 at 12:37 PM Carsten Schoenert wrote: > 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

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

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

The way we have split things up now, the nightly docs are not the appropriate pairing for the V6 stable release -- they may diverge over time. I think the vast majority of Linux users also have access to the Internet and so directing them to the most up-to-date docs is the right move. I am not sa

Re: [Kicad-developers] V6 documentation

On 1/19/22 12:00 PM, Jon Evans wrote: That just doesn't seem that useful to me.  The fact that Fedora forces this process means that Fedora offline docs will always be outdated. I don't disagree, but really, we could say that everything is always outdated - the code, the libs etc. I have to

Re: [Kicad-developers] V6 documentation

That just doesn't seem that useful to me. The fact that Fedora forces this process means that Fedora offline docs will always be outdated. If there is no way to work around it for Fedora, I suggest we develop an out-of-band way of delivering offline docs to people (not using the Fedora packaging

Re: [Kicad-developers] Possible build failure using gcc 12

Ok - I learned something new - thanks! Here is the issue: https://gitlab.com/kicad/code/kicad/-/issues/10508 Steve On 1/19/22 11:51 AM, Seth Hillbrand wrote: Hi Steven, You can report this on the tracker, just add the term "build-error" to the description.  I think we list this in t

Re: [Kicad-developers] Possible build failure using gcc 12

Hi Steven, You can report this on the tracker, just add the term "build-error" to the description. I think we list this in the template as an option but it might be in the middle of the text instructions. Seth On Wed, Jan 19, 2022 at 7:20 AM Steven A. Falco wrote: > The Fedora nightly builds

Re: [Kicad-developers] V6 documentation

Right now, the downstream (official) Fedora builds depend on a single tag for all the components - source code, libraries, and docs. I could substitute a SHA for the docs, but I'd have to hard-code the SHA in the "spec file" that controls the build, the same way the tag is hard-coded in the sp

Re: [Kicad-developers] V6 documentation

I think we are saying the same thing? The other parts of what I said were to ensure it is downloadable for offline use. When I say "online documentation," I mean: 1. it is html files viewed from a browser 2. the most up-to-date version is online and updated rapidly (instantly) as new docu

Re: [Kicad-developers] V6 documentation

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. The majority of users will be served better by keeping a "rolling release" online at docs.kicad.org (with a download button, ideally). > It absolutely doesn't hurt to

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

Oh, ok. I agree with this. I'd be fine with downloading the code separate from the documentation and not packaging them together. The documentation released separately just needs to clearly state which software version it goes with is all. Thanks! Gabriel Staples (sent from my Android) Le mer.

Re: [Kicad-developers] V6 documentation

I am not saying offline documentation isn't important. I'm saying offline documentation *bundled with a specific KiCad release* isn't important. If someone needs offline documentation, we should make it easy for them to obtain the latest "snapshot" of any given doc branch from our website. Just b

Re: [Kicad-developers] V6 documentation

> I'm not sure that this is a very important feature in today's world. In many parts of the government, and in some research labs, offline documentation is still **very important** because they block nearly all of the internet. But, a healthy compromise would be to have online documentation only,

Re: [Kicad-developers] V6 documentation

I agree that if the same documentation is taken as a snapshot of the latest version at that time, it must be clearly noted for the user (and maybe together with a note it is likely out of date compared to the online version). I will read the README files and we can go from there. Haven't really us

[Kicad-developers] Possible build failure using gcc 12

The Fedora nightly builds succeeded on F34 and F35 last night, but failed on Rawhide. Rawhide recently switched to gcc 12, so that might be the cause of the build failures. I would write this up as an issue on gitlab, but the template requires version information, which is not applicable in t

Re: [Kicad-developers] V6 documentation

The documentation lives in this git repo: https://gitlab.com/kicad/services/kicad-doc The same sources build the version on the website (docs.kicad.org) and the offline docs. If keeping the offline docs is important, I think the next best thing is to insert some extra text in the offline build th

Re: [Kicad-developers] V6 documentation

In my opinion it is great to have fall-back plan such as built in documentation (which is particularly handy if you lost internet connection) but at the moment it is too different from online version which is why I raised this question. Assuming there is a reasonably easy way to export online docs

Re: [Kicad-developers] V6 documentation

On Wed, Jan 19, 2022 at 08:02:51AM +, Martijn Kuipers wrote: > If separate, you could update it more frequently. Just take care it is > understandable for which lkicad version it applies. > > Local docs is where I look first. Version matching should be handled by the packaging system in use,

Re: [Kicad-developers] V6 documentation

If separate, you could update it more frequently. Just take care it is understandable for which lkicad version it applies. Local docs is where I look first. Just my 2cents. Martijn A quarta, 19/01/2022, 05:44, Ajith Narayanan escreveu: > Greetings! > > KiCad's documentation is in a standard so