Re: MX-TDE edition options (need a debian TDE dev)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thursday 23 July 2020 09:55:38 am Slávek Banko wrote:
> On Thursday 23 of July 2020 16:46:21 Michael wrote:
> > On Thursday 23 July 2020 06:07:25 am Dr. Nikolaus Klepp wrote:
> > > Anno domini 2020 Mon, 20 Jul 13:23:27 -0500
> > >
> > >  Michael scripsit:
> > > > On Monday 20 July 2020 12:28:48 pm Dr. Nikolaus Klepp wrote:
> > > > > Anno domini 2020 Mon, 20 Jul 11:31:17 -0500
> > > > >
> > > > >  Michael scripsit:
> > > > > > On Sunday 19 July 2020 07:21:09 pm Michael wrote:
> > > > > > > This seems too easy.
> > > > > > >
> > > > > > > ###########
> > > > > > > by dolphin_oracle » Sun Jul 19, 2020 12:05 pm
> > > > > > > the files that we use to define what's in
> > > > > > > mx-packageinstaller->popular apps are XML files. there are
> > > > > > > even places for screenshots, pre and post install scripts if
> > > > > > > extra steps are needed, like adding repos.
> > > > > > >
> > > > > > > https://github.com/MX-Linux/mx-packageinstaller-pkglist
> > > > > > > ###########
> > > > > > >
> > > > > > > I found 4 examples with external repositories
> > > > > > >
> > > > > > > https://github.com/MX-Linux/mx-packageinstaller-pkglist/search
> > > > > > >?q=re posi tory &unscoped_q=repository
> > > > > > >
> > > > > > > To me ‘spotify_64.pm’ seems the closest match to what I
> > > > > > > believe we’d want.  ‘airvpn.pm’ is the most complex, probably
> > > > > > > good for example/reference. In any event I copy/pasted/edited
> > > > > > > what I could (attached as tde_64.pm). Which probably needs to
> > > > > > > go into the TDE git somewhere.
> > > > > > >
> > > > > > > Things that definitely need checking:
> > > > > > >
> > > > > > > - <installable> architecture(s) (I picked 64, not completely
> > > > > > > sure that’s correct).
> > > > > > > - method/place for # Import GPG signing key.  (needs review by
> > > > > > > MX dev). - when to use sudo and when it’s not needed (got no
> > > > > > > real clue why some commands use it).
> > > > > > > - <description> needs an official English description and then
> > > > > > > as many translations as we can do.
> > > > > > >
> > > > > > > We also need a TDE developer to interface with dolphin_oracle
> > > > > > > directly for the ‘official’ request to add it to their system.
> > > > > > >
> > > > > > > Anything else I can help with let me know,
> > > > > > > Michael
> > > > > >
> > > > > > - Updated .pm per dolphin_oracle comments.
> > > > > >
> > > > > > - Could use newer screenshot(s) posted to:
> > > > > > - - https://www.trinitydesktop.org/screenshots.php
> > > > > > - - All those are from 2014.
> > > > > > - - If at all possible do one similar to
> > > > > > https://www.trinitydesktop.org/media/screenshots/large/tde1.png
> > > > > > so that it includes the full, visible, "The Trinity Desktop is a
> > > > > > full software desktop..." paragraph.  (but possibly I don’t
> > > > > > understand the use of that screenshot, so maybe not?)
> > > > > >
> > > > > > - .pm should be renamed to tde.pm if TDE is all architecture.
> > > > > >
> > > > > >
> > > > > > https://forum.mxlinux.org/viewtopic.php?f=93&t=59309
> > > > > >
> > > > > > > ###########
> > > > > >
> > > > > > by dolphin_oracle » Sun Jul 19, 2020 8:13 pm
> > > > > > you don't need sudo anywhere. the script runs elevated already.
> > > > > >
> > > > > > if your packages are 64bit only, the 64 is appropriate. If you
> > > > > > also have 32 bit packages, then "all" is appropriate.
> > > > > >
> > > > > > you will want to run an apt-get update in the post-uninstall
> > > > > > area since you are removing a list. typically I don't remove
> > > > > > list files unless there is a chance of some conflict, in which
> > > > > > case they should not be left enabled at all. (deb-multimedia is
> > > > > > an example here, good packages, but leaving the repo enabled is
> > > > > > bad for mx).
> > > > > >
> > > > > > for the key, download into /tmp instead of /root. remove the
> > > > > > temporary downloaded deb after install.
> > > > > >
> > > > > > we prefer the deb-src entries to be commented out by default.
> > > > > > our debian.list file is a good example.
> > > > > >
> > > > > > > ###########
> > > > >
> > > > > @ screenshots: there where a number of newer ones on the site,
> > > > > too. I remember that some of my FreeBSD box where there, too, as
> > > > > TDE does quite nicely on FreeBSD these days. Don't know when they
> > > > > vanished, where and why.
> > > >
> > > > Hopefully last edit of the .pm by me...
> > > >
> > > > I'm scheduled to test it next weekend, I'll update to the list next
> > > > then (these minor edits are getting spammy, so see the MX formum
> > > > post till then)
> > > >
> > > > best all, michael..
> > >
> > > Hi Michael,
> > >
> > > When I have MX installed, whet do I do with that tde.pm ?
> >
> > Hi Nik,
> >
> > Notes:
> > 1) This has not been tested!  Do scan for typo’s before use.  (wget line
> > was tested)
> > 2) I’ve set the attached .pm for 64 bit architectures.  (change as
> > needed) 3) AFAIK this only works if you’ve installed the full MX.  (so
> > you’ll already have Xfce4 installed)
> >
> > After the MX install, drop it in:
> >
> > /usr/share/mx-packageinstaller-pkglist
> > -rw-r--r--    root root
> >
> > Then from Xfce4
> >
> > Menu >> MX Tools >> MX Package Installer
> > {Tab} Popular Applications
> > {Expand} Desktop Environments
> > {Check} Trinity Desktop Environment
> > {Click} Install
> >
> > Logout of Xfce4
> > Login TDE
> > {set default window manager, etc.}
> >
> > I think that’s it.  Let me know how it goes :)
> >
> > Best,
> > Michael
> >
> > Notes continued:
> > 4) Still needs translations of the description.
> > 5) Has several extra, extraneous comments.
> >
> > Ref:
> > https://forum.mxlinux.org/viewtopic.php?p=587347#p587347
>
> Is it necessary to have files for each architecture? Is it possible for one
> file to provide that information for all architectures?
>
> I haven't looked at what architectures are supported in MX, but I assume we
> provide packages for all the needed architectures. Because the repository
> URL is the same for all architectures, and therefore the same GPG key, it
> seems unnecessary to create multiple files that will contain the same
> data, only with a difference for the architecture.

Hi Slávek,

That was one of my questions earlier in this thread, "What architecture is 
TDE?"  Based on above, I'm changing it to 'all.'

---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting





[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux