Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
-
Hello, can someone tell me where I can find the source code for the installer? It looks like the "Setup" directory got dropped from the source tree along the way. It should include some .iss files and other things. Thanks.
-
Hello,
yes, we have removed the setup folder for now because we are completely reworking that right now. But you can simply use an older version if there is a need. What do you need a custom setup for?
regards,
PhilipPhilip
Team pdfforge -
As in the installer source for 1.3.x is the same as 1.4.x or you aren't releasing the source for 1.4.x? 1.4.3 is the current stable release right? I'm not really interested in a custom installer, just more to see what its doing and where the problems might be to give you a heads up. Like I installed on a computer the other day and its complaining about not being able to find a ghostscript .dll.
-
Ah, ok. Yes, the parts around the PDFCreator installation and specially Ghostscript are the same in the 1.3.x branch. PDFCreator telling that there was no ghostscript.dll is strange though.
You could have a look at your options -> Ghostscript and see if there are orphaned GS installations on your system or something like that.
regards,
PhilipPhilip
Team pdfforge -
OK fine, but you still haven't actually answered any of my questions, so I will state them clearly here.
1. Can someone tell me where I can find the source code for the installer?
2. As in the installer source for 1.3.x is the same as 1.4.x or you aren't releasing the source for 1.4.x?
3.1.4.3 is the current stable release right?
-
Hello,
I am very sure I have, but I'll gladly do it again:
1. You can find it together with the releases on sourceforge or in the sourceforge svn. You can jump back in the revisions/tags to get the setup. I supposed you knew that as you have pointed that out.
2. These are two questions. I have answered the first, the install procedures for PDFCreator are basically the same and should work. The second: There is currently no release of the setup code, but we'll bring that live again once it is cleaned up.
3. yes.
I hope this now really answers your questions.
kind regards,
PhilipPhilip
Team pdfforge -
OK thank you!
-
What license is the 1.3.x installer source code released under? I can't find where that is documented.
-
Nice guy that you go to sourceforge and open a ticket with weird claims there... Please actually *read* what I have written.
Philip
Team pdfforge -
If your software was truly open source at a minimum users would be free to examine and/or modify the install source code for the 1.4.x series. Older source code that is "basically the same and should work" does not meet open source disclosure requirements. What are the differences? Why are you so afraid to release the source code for this version? What is going on with the installer that you don't want people to see?
For those interested, the sourceforge ticket is here:
-
There is nothing secret in the installer, but please, please actually read what I have written before. We have started reworking the setup source and will put it into the repository once this is finished. You can use and examine the old setups in the meantime.
Despite that: Not every part of our software is OpenSource. You can't examine the Microsoft DLLs, you can't examine the Windows printer system. If we would use MSI you would not even know what the installer system does. Depending on the Setup Packaging tool there would also not be a source for the setup at all that could be released, like with InstallAware that we have been trying out some time ago.
The setup is the least interesting part of the Software in my eyes. If you want to use or have a look at the setup, use the one from the 1.3.x branch for now or wait until we have finished the work on that.
Philip
Team pdfforge -
I keep reading what you said and I am still confused. Can you please clarify? You are saying 1.4.3 and all previous 1.4 releases aren't "finished?" If so why did you release them?
