Hello,
for info. When connecting on the OBS with the guest account you can use
the osc command.
osc help dependson
dependson (whatdependson): Show the build dependencies
The command dependson and whatdependson can be used to find out what
will be triggered when a certain package changes.
This is no guarantee, since the new build might have changed dependencies.
dependson shows the build dependencies inside of a project, valid for a
given repository and architecture.
NOTE: to see all binary packages, which can trigger a build you need to
refer the buildinfo, since this command shows only the dependencies
inside of a project.
The arguments REPOSITORY and ARCH can be taken from the first two columns
of the 'osc repos' output.
usage in package or project directory:
osc dependson REPOSITORY ARCH
osc whatdependson REPOSITORY ARCH
usage:
osc dependson PROJECT [PACKAGE] REPOSITORY ARCH
osc whatdependson PROJECT [PACKAGE] REPOSITORY ARCH
dominig@intel09:~>
Should help.
Please note that all dependency do not need to be explicitly described
in OBS, as you have the boot strap which is always copied in the chroot
and indirect dependencies which are more complex to manage.
You have two tools which can help you as well :
- agilebrower from the meego project tools which works on binary packages.
- rpmgraph http://www.rpm.org/max-rpm-snapshot/rpmgraph.8.html
under Yocto with the integrated tools.
Dominig
Le 05/01/2015 10:37, Ankur Garg a écrit :
> Samsung Enterprise Portal mySingle
>
> Hi Patrick,
>
> Thanks for pointing that out. I have modified the script to check the
> .spec file instead of the CMakeLists.txt.
>
>
>
> Thanks,
>
> Regards,
>
> Ankur Garg
>
>
>
> ------- *Original Message* -------
>
> *Sender* : Patrick Ohly<[email protected]>
>
> *Date* : Jan 05, 2015 14:29 (GMT+05:30)
>
> *Title* : Re: [Dev] [New Tool Addition] Correct location to add the tool
>
>
>
> On Mon, 2015-01-05 at 08:50 +0000, Ankur Garg wrote:
> > Hi,
> >
> > I've developed a tool for dependency-check.
> >
> > For a given package name, the tool lists out all the projects which
> > have that package as their dependency in the CMakeLists.txt
>
> Why do you base it on CMakeLists.txt instead of the .spec file?
>
> Not all projects use cmake, so the tool will miss dependencies. While a
> partial list of dependencies may still be useful, there's also the risk
> that this limitation gets forgotten and then someone is misled by the
> tool's output.
>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> https://lists.tizen.org/listinfo/dev
--
Dominig ar Foll
Senior Software Architect
Intel Open Source Technology Centre
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
