@ffesti Brought the discussion from #2580 to here.

> This PR needs to be against master. Also a feature like this needs at least 
> some documentation. installplatform is a script no one ever should need to 
> look into. So hiding features in there is not acceptable. May be adding a 
> section to INSTALL is a good first step. We can move that to the docs/manual 
> later on if we feel it take up too much space there.

I added the documentation text in INSTALL after the default make install line.

> I am also wonder if we should allow passing the directory name.

I don't know. At this point it's still RFC both for rpm and the Yocto 
community. But it allows me to run rpmbuild straight on the target system.

> I might have missed something but it looks like there can only be a "custom" 
> platform.

One is enough. There is only a single target platform you can build for at a 
time.

See the complete patch at 
https://lists.openembedded.org/g/openembedded-core/message/184844

> So please re-open this against master.

See #2585  


-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2578#issuecomment-1651772114
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/2578/1651772...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to