Folders in Repo not being included in GISO Image

[ajackson79]

I have tried this a few times now and based on the Readme file example below I assume the gisobuild script would support folders.

$ tree /path/to/repo/
/path/to/repo/
├── bugfixes
│   ├── 8000-x64-24.3.1-CSCab12345.tar.gz
│   ├── 8000-x64-24.3.1-CSCzy54321.tar.gz
│   ...
└── optional-rpms
    ├── cdp
    │   ├── xr-cdp-0deb3755978fea2a-24.3.1v1.0.0-1.x86_64.rpm*
    │   ├── xr-cdp-1b7551b6d2623937-24.3.1v1.0.0-1.x86_64.rpm*
    │   ├── xr-cdp-24.3.1v1.0.0-1.x86_64.rpm*
    │       ...
    ├── telnet
    │   ├── xr-telnet-0deb3755978fea2a-24.3.1.22Iv1.0.0-1.x86_64.rpm
    │   ├── xr-telnet-24.3.1.22Iv1.0.0-1.x86_64.rpm
    │       ...
        ...

It doesn't work for me though unless all the tar files and the RPMs are in the root of the repo. I have recreated the repo many times with different folder structures and the packages are added to the repo each time I create it. When I create the GISO image though the only one that includes the tar and rpms is the one where they are all in the root of the repo. Is this expected behavior?

[NeilKetley]

Sorry about this, the README documentation is wrong, as you've noticed :-( If the RPMs, tarballs etc. are not all in one folder then the location of each folder would need to be separately specified to the --repo argument. There is though no requirement to use separate folders, but of course in some cases that may be convenient.

So, in the example structure above, the --repo argument would need to look like this:

--repo /path/to/repo/bugfixes /path/to/repo/optional-rpms/cdp /path/to/repo/optional-rpms/telnet

We'll get the README fixed up. Thanks for raising this!

[ajackson79]

Okay thank you for updating the documentation and giving me the additional info for using multiple repos. That could come in handy for structuring things.

[ajackson79]

One other thing I noticed is for the NCS 540 when you download the SMU files it is a tar inside a tar so you have to untar every file once because the giso utility doesn't go 2 levels deep with those tar files.

[NeilKetley]

Would you mind raising a separate issue for the problem with handling the NCS540 SMU? That would need to be passed on to a different team and it would be helpful to have a new issue to avoid confusion!

[ajackson79]

created new issue

[NeilKetley]

Thanks. I have forwarded it on to the relevant team for their attention.