Re: [oi-dev] Tasks to focus on
On 2021-01-24 08:29, Gary Mills wrote: On Sat, Jan 23, 2021 at 02:35:01PM -0700, Nelson H. F. Beebe wrote: I'm part of the TeX Live team that every (northern) winter produces a new release; many O/S distributions then take up that release and repackage it according to their preferences. That's probably what Openindiana would do too. All software products installed on OI systems are installed from IPS packages, the same as on Solaris. The packages are built from source. Binaries are of no use for OI packages. First, though, there has to be demand for the software product. I, myself, have no interest in Tex. In fact, I don't even know what Tex is, except that it's used by mathematicians. I'm not one of those. I have some doubts about the demand. Type1 fonts are made available. Type1 fonts are often also embedded in PDF files, and other places where fonts can be embedded. IMHO Tex to be a valuable addition to OI. [...] However, at Utah, I make a point of doing test builds for many more, and I can report that this year, with newer compilers on Oracle Solaris 11.4, there were few problems in building a complete TeX Live 2021 set of binaries. The current status report is here: http://www.math.utah.edu/pub/texlive-utah/ I've read this quickly, and already see obstacles. OI packages have some restrictions that may not arise when the software is installed directly. o All software is installed in system locations, mostly under /usr . Configuration files go under /etc . Log files go under /var . PID files are installed in /var/run . o There are no private libraries, and no static libraries. All libraries are shared, in both senses of the word. Libraries are often supplied by other packages, and often other products. o User software does not distinguish between Intel, AMD, or other compatible CPUs. o 32 and 64-bit binaries go in the same package, although omitting the 32-bit versions is acceptable too. o Packages cannot interfere with each other unless they are alternative versions of similar products. The package build process installs the files into a prototype directory. Then the publish process builds the actual package from files in the prototype directory. Packages are made available by a package server, from which users can install them on their own systems. --Chris -- ~10yrs a FreeBSD maintainer of ~160 ports ~40yrs of UNIX ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Tasks to focus on
On Sun, 24 Jan 2021, Gary Mills wrote: First, though, there has to be demand for the software product. I, myself, have no interest in Tex. In fact, I don't even know what Tex is, except that it's used by mathematicians. I'm not one of those. I have some doubts about the demand. While I did buy a couple of books on TeX a long time ago (and even wrote a resume in it once) it did not catch on for me. However, I have learned that TeX is a wonderful typesetting/publishing system (with fonts!) which can be taken advantage of by other software. This means that if you want to produce a PDF, or Postscript for a printer, may be useful to have TeX available. For example, I have written documentation using the reStucturedText text format, and used reStucturedText tools which themselves used TeX under the covers to produce nice PDF output. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Tasks to focus on
Hi Gary! > On Sat, Jan 23, 2021 at 02:35:01PM -0700, Nelson H. F. Beebe wrote: > > > > I'm part of the TeX Live team that every (northern) winter produces a > > new release; many O/S distributions then take up that release and > > repackage it according to their preferences. > > That's probably what Openindiana would do too. All software products > installed on OI systems are installed from IPS packages, the same as > on Solaris. The packages are built from source. Binaries are of no > use for OI packages. > > First, though, there has to be demand for the software product. I, > myself, have no interest in Tex. In fact, I don't even know what Tex > is, except that it's used by mathematicians. I'm not one of those. I > have some doubts about the demand. I use it every day. :-) TBH it's a self-built version on Solaris 11.3. > [...] > > However, at Utah, I make a point of doing test builds for many more, > > and I can report that this year, with newer compilers on Oracle > > Solaris 11.4, there were few problems in building a complete TeX Live > > 2021 set of binaries. > > > > The current status report is here: > > > > http://www.math.utah.edu/pub/texlive-utah/ > > I've read this quickly, and already see obstacles. OI packages have > some restrictions that may not arise when the software is installed > directly. TeX (in the form of TeXlive 2020) is available as an IPS package from the OmniOS "extra" repository, so packaging is no problem. Regards -- Volker -- Volker A. BrandtConsulting and Support for Solaris-based Systems Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: v...@bb-c.de 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" ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Tasks to focus on
On Sat, Jan 23, 2021 at 02:35:01PM -0700, Nelson H. F. Beebe wrote: > > I'm part of the TeX Live team that every (northern) winter produces a > new release; many O/S distributions then take up that release and > repackage it according to their preferences. That's probably what Openindiana would do too. All software products installed on OI systems are installed from IPS packages, the same as on Solaris. The packages are built from source. Binaries are of no use for OI packages. First, though, there has to be demand for the software product. I, myself, have no interest in Tex. In fact, I don't even know what Tex is, except that it's used by mathematicians. I'm not one of those. I have some doubts about the demand. [...] > However, at Utah, I make a point of doing test builds for many more, > and I can report that this year, with newer compilers on Oracle > Solaris 11.4, there were few problems in building a complete TeX Live > 2021 set of binaries. > > The current status report is here: > > http://www.math.utah.edu/pub/texlive-utah/ I've read this quickly, and already see obstacles. OI packages have some restrictions that may not arise when the software is installed directly. o All software is installed in system locations, mostly under /usr . Configuration files go under /etc . Log files go under /var . PID files are installed in /var/run . o There are no private libraries, and no static libraries. All libraries are shared, in both senses of the word. Libraries are often supplied by other packages, and often other products. o User software does not distinguish between Intel, AMD, or other compatible CPUs. o 32 and 64-bit binaries go in the same package, although omitting the 32-bit versions is acceptable too. o Packages cannot interfere with each other unless they are alternative versions of similar products. The package build process installs the files into a prototype directory. Then the publish process builds the actual package from files in the prototype directory. Packages are made available by a package server, from which users can install them on their own systems. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Tasks to focus on
Great news below on building TeX live. Also please note that I don't question or doubt, that it can be built; But it must be maintained, somebody has to look after the updates and so on. If for OpenIndiana it would be possible to simply "pkg install tex" or "pkg install texlive" that would be nice. Anyway as some "OpenIndiana task to focus on", adding TeX I'd appreciate that. I haven't looked at other TeX distributions but perhaps some minimal approach like MikTeX could also be useful. Regards, David Stes - Op 23 jan 2021 om 22:35 schreef Nelson H. F. Beebe be...@math.utah.edu: > The current status report is here: > > http://www.math.utah.edu/pub/texlive-utah/ > > The section on Solaris 11.4 on amd64 is at this URL: > > http://www.math.utah.edu/pub/texlive-utah-2021/README.html#solaris-11.4 > > I have several machines running various releases of the Illumos / > OpenIndiana / Omnios / Tribblix / ... family, and I'll attempt a > similar build on one or more of those systems in the next week or two. > --- > > - Nelson H. F. BeebeTel: +1 801 581 5254 - > - University of UtahFAX: +1 801 581 4148 > - > - Department of Mathematics, 110 LCBInternet e-mail: be...@math.utah.edu > - > - 155 S 1400 E RM 233 be...@acm.org be...@computer.org > - > - Salt Lake City, UT 84112-0090, USAURL: http://www.math.utah.edu/~beebe/ > - > --- ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Tasks to focus on
> I use here the openCSW package, a little bit matured bu it works But the openCSW package, is it getting updates that are automatically updated then; within an OpenIndiana "pkg update" if one updates the OpenIndiana system ? There may be solutions (somebody suggested to simply compile texlive from source on OpenIndiana, which presumably is also the most straightforward way that the texlive developers also would like to see). But on the other hand from the OI perspective, a : pkg install texlive without a need to define additional publishers would be nice, and would also be useful to be able to upgrade TeX or texlive within OI updates. Such a project may be easy for experienced packagers, I don't know. Maybe on "github" there is something (github actions ?) to collect such projects or ideas, or tasks to work on, and then people who want to contribute and work on something could react on github. Aurélien : instead of emailing the "Tasks to focus on" why not create github projects or actions for each of those ideas ? I think that the skills of Gary Mills (C language and Perl) would be or could be a good match for something like texlive, which involves mostly command line. David Stes ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
