Hi Gary!
Great job! Sorry I couldn't contribute much. > First of all, how much interest do you have in OI on SPARC? My > interest is as a developer and tester. What is your interest? > I'd like to determine the size of the audience. My plan is to install it into an LDOM with the control domain being Solaris. TBH I don't know when I'll find the time. > > How should I contribute to OI on SPARC? I have plans to build more > packages, and to do so with fewer changes to the OI source. I also > have plans to update the distribution from the current 2018 to 2019 or > 2020. Does this sound reasonable to you? This sounds absolutely reasonable. As OI "hipster" (hate that name) is a rolling release distro, the update 2018 -> 2019 may be gradual. > How should you contribute to OI on SPARC? I've filed bug reports > for many of the changes I've made. They can be seen at: > > https://www.illumos.org/projects/openindiana/issues > > I've attached patches to each bug report, but in order for these > patches to be integrated into the OI source, the patches need to be > turned into PRs for github. I think it's important to differentiate between OI and Illumos here. There's things you compile from the Illumos source, and there's packages from upstream that need to be patched for OI SPARC, and ideally the patches should be upstreamed again. > They also need to be tested on x86 to > make sure they don't accidentally change anything there. Can you help > with any of this? Can you build packages for SPARC from OI source? > Can you help in any other way? *sigh* ENOTIME > What type of repository do you prefer? Should it be file-based, as it > is now, or should it be remote, as for OI x86? The repository will > only get larger, as people build more packages and publish them. Will > you download such a large file? I don't know of any way to merge > repositories, so there must be only one. A file-based repo is only a temporary kickstart. In the end a repo should be served via a depot daemon instance to be usable. It is very easy to pull the contents from one repo into another repo; just use the "pkgrecv" command. The point is who will shoulder the time and effort to host the repo. Ideally, there would only be one repo offering "fat" packages, i.e. package containing both SPARC and x64 binaries managed by variants. I know that this will never happen because it is a lot of work and most OI devs aren't that interested in SPARC. > Finally, who should coordinate OI on SPARC? Should this be done by > the OI project, or should it be done separately? Since you have been doing the heavy lifting, you should just do as you see fit. Code speaks louder than words. :-) > Keep in mind that OI > SPARC uses OI source. Most of it builds and publishes with no > changes. When changes are necessary, my plan has been to introduce > them with no harm to x86 packages built from the same source. Indeed, > some of the changes fix bugs in the corresponding x86 packages. This is a very valuable result. As Garrett D'Amore once said: "SPARC keeps us honest". > Also > keep in mind that IPS is designed to handle multiple architectures, > making it easy to integrate SPARC with x86. In fact, this is already > done for illumos. That last part I don't understand (not having looked at you repo yet). Do you ship IPS packages with both SPARC and x64 actions? Best regards -- Volker -- ------------------------------------------------------------------------ Volker A. Brandt Consulting and Support for Solaris-based Systems Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim, GERMANY Email: [email protected] Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 46 Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt "When logic and proportion have fallen sloppy dead" _______________________________________________ openindiana-discuss mailing list [email protected] https://openindiana.org/mailman/listinfo/openindiana-discuss
