[packagekit] PackageKit and source packages?

[Richard Hughes]

On 23 May 2011 09:58, Anders F Björklund <afb at algonet.se> wrote:
> For the backends that already compile from source (ports),
> these would just resolve to the same package I suppose ?

I guess.

> Shouldn't the arch be changed too, to download the source
> rather than a pre-compiled version if one is available ?

Yes, sorry, that was my mistake. It should have been something like
Package(available, sane;0.3.0;src;fedora-source, Scanner software)

> When you install, it tries to download a binary .tbz if one
> is available otherwise it falls back to building from source.

Makes sense.

>> ->   DownloadPackage(sane;0.3.0;i396;fedora-source, "/tmp")
>> <-   Package(downloading, sane;0.3.0;i396;fedora-source, Scanner software)
>> <-   Files(sane;0.3.0;i396;fedora-source, "/tmp/sane-0.3.0.i396.srpm")
>> <-   Finished()
>
> That should probably be more like .src.rpm than .i386.srpm ?
> Relating to the arch question above, shouldn't it be "src".

Yup, sorry.

>> or, if we just want the files list of the source package:
>>
>> ->   GetFiles(sane;0.3.0;i396;fedora-source, "/tmp")
>> <-   Files(sane;0.3.0;i396;fedora-source, "/usr/share/sane/README")
>> <-   Finished()
>
> So when you query a source package, you get the files that
> would be installed - e.g. build and peek at $RPM_BUILD_ROOT ?

Yup. It's easy for a src.rpm as the file list is in the metadata, but
for building-as-src distros, it might just be sane to emit
NO_SUPPORTED.

> It seemed more likely that it would consist of files like
> *.spec and *.tar.gz (or similar, like *.patch *_orig.tar.gz)

I think that's also a sane thing to do.

> Would PackageKit also support for BuildDepends and BuildPackage ?
> Or is this more of an informational query, like a metadata field ?

Yup, I see it more of an informational thing than an interface for
building. That would get complex really quickly in my opinion.

Richard.