The CI/CD auto created .package from the CfUnit project ended up as a mess! It contains all kind of artefacts which do not belong in it... See the auto created .package as attachment (just unzipt it).
I had a quick look, but didn't find what's wrong. I was not able to install the package, but the content looked good. That we pack everything from the subfolder, which contains the package.manifest is a design decission. It makes things a bit easier. We just copy everything, but the package installer installs just the parts, which are defined in the manifest.
One thing, is that it makes the package build more simple. The second thing is, that it is also no bad idea to include the sources into a package, when you deliver an open source project ;)
But I didn't find the reason why this package doesn't want to install on my CODESYS installation. Did you encounter a simimlar problem?
BR,
Ingo
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You say you found nothing wrong, but then you say the package does not install. To be honest, that is contradictive ;-)
First thing I did is install the new .package as I was very curious. It failed :-( and I unzipped it immediatly to check. Then I saw all these superfluous files (the overhead from your design decission as explained). As the install failed, I thought the reason is the extra content, so I did not bother to search for the fault. What I did instead of searching the error is starting this ticket.
Plus, I want to have full control over the manifest, which should be possible as the documentation says, but I really don't see how? Could you please explain via an directory example where the manifest file can found and changed?
cfunit.compiled-library,
cfunit.ico,
cfunit.library, cfunit.library.md, (0kb! => ??)
cfunit.library.xml,
cfunit.package,
cfunit.allusers.opt,
CfUnitTimedTestExample.project,
CfUnitTimedTestExample.md,
CfUnitTimedTestExample.xml,
CfUnitVerifier.gif,
CfUnitVerifier.project,
CfUnitVerifier.project.md
CfUnitVerifier.project.xml,
CfUnitVerifierOutput.xml,
CfUnit-wineuser-ed001221eb42.opt,
icon.png,
license.txt,
package.manifest,
SimpleCfUnitExample.project,
SimpleCfUnitExample.project.md,
SimpleCfUnitExample.project.xml.
Every .project.md file should be bigger then 0kb as far as I know, so something went wrong while creating cfunit.library.md
Anyway thank you for explaining why the package contains these files (as by design) so you guessed it, you should really explain the reason behind the extra files in the documentation(!)
Also, I saw that CI/CD documentation contains a lot of misspellings etc. If you give me some rights to edit that page, I can help you with it.
with kind regards,
Aliazzz
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the package.manifest of package v1.0.0.0 is already exactly yours. It is only auto-generated if there is none found. So yours is taken. The installation problem, which I got was due to a duplicate package Id (maybe only in my, potentially corrupted, installation). But thanks on the input about the additional generated files. This should really not be.
BR,
Ingo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I really don't get it. Beside the *.opt files, you committed all those files into the tags directory v1.0.0.0. So I currently see none which was accidently autogenerated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Aliazzz,
I had a quick look, but didn't find what's wrong. I was not able to install the package, but the content looked good. That we pack everything from the subfolder, which contains the package.manifest is a design decission. It makes things a bit easier. We just copy everything, but the package installer installs just the parts, which are defined in the manifest.
One thing, is that it makes the package build more simple. The second thing is, that it is also no bad idea to include the sources into a package, when you deliver an open source project ;)
But I didn't find the reason why this package doesn't want to install on my CODESYS installation. Did you encounter a simimlar problem?
BR,
Ingo
You say you found nothing wrong, but then you say the package does not install. To be honest, that is contradictive ;-)
First thing I did is install the new .package as I was very curious. It failed :-( and I unzipped it immediatly to check. Then I saw all these superfluous files (the overhead from your design decission as explained). As the install failed, I thought the reason is the extra content, so I did not bother to search for the fault. What I did instead of searching the error is starting this ticket.
Plus, I want to have full control over the manifest, which should be possible as the documentation says, but I really don't see how? Could you please explain via an directory example where the manifest file can found and changed?
cfunit.library.md, (0kb! => ??)
Every .project.md file should be bigger then 0kb as far as I know, so something went wrong while creating cfunit.library.md
Anyway thank you for explaining why the package contains these files (as by design) so you guessed it, you should really explain the reason behind the extra files in the documentation(!)
Also, I saw that CI/CD documentation contains a lot of misspellings etc. If you give me some rights to edit that page, I can help you with it.
with kind regards,
Aliazzz
Hi Aliazzz,
the package.manifest of package v1.0.0.0 is already exactly yours. It is only auto-generated if there is none found. So yours is taken. The installation problem, which I got was due to a duplicate package Id (maybe only in my, potentially corrupted, installation). But thanks on the input about the additional generated files. This should really not be.
BR,
Ingo
I really don't get it. Beside the *.opt files, you committed all those files into the tags directory v1.0.0.0. So I currently see none which was accidently autogenerated.
You can close this ticket as things are more clear now