Hello Thomas,
2007/10/23, Thomas Wagner <Thomas.Wagner at sun.com>:
>
> - 1-click/hands-off setup for the build-environment
>
> - documentation how to integrate pkgbuild/pkgtool/common-build-environment
> and SunStudio into a Distribution (think indiana/belenix/all others).
>
> - pkgbuild --parseable-softwarelist
> to feed this output into a local Index in e.g. a Software-Selection
> Menu to the end-user/Administrator
>
> - relocatable packages, e.g. student installes his own copy of program
> SFExchat into his $HOME
> this would make the Admin-intervention obsolete (think:
> Workstation-Pool)
> he/she selects the software from a Software-Selection Menu
This is impossible to do at package level cause packages mostly have links
in their source code.
In build level it can be done, but in such case I suggest to support some
profiles.
Default profile wouldn't change %{_bindir}, %{_mandir} and others ..
User created profile could change these default paths to something else.
Building would look like this:
pkgtool --profile=user_profile --download build -v package.spec
- instant-build
> Software-Selection Menu provides un-build Software, if selected
> dependencies are resolved and Sources are fetched and build
> instantly
>
> - click-and-build URL support.
> User clicks on a URL on the Web/chat/Email and pkgbuild
> does an instant build
>
This could be more interesting for binary repositories that for compile
ones.
Regards,
Petr
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20071023/6338cd59/attachment.html>
