Please don't do that yet. There are a lot of packages in our current TEI debs, many of which have nothing to do with us (such as rnc). We may elect to continue maintaining only the ones that are our business, to make our life simpler, and to my mind, a package for Oxygen is not really our business. It's a piece of commercial software. Either Syncro should provide a deb, or someone might do it as a personal project, but should it be a TEI project? We certainly have a big role in helping to maintain the TEI framework, but distributing the software itself is a different issue. Cheers, Martin On 15-09-24 09:41 AM, Kevin Hawkins wrote:
So the package updates not just the stylesheets but also oXygen itself? If so, I'll update the wiki to make this clear.
On 9/24/15 11:37 AM, James Cummings wrote:
The benefit, if the package was maintained, is that those of us using ubuntu or debian never have to think to install a new version of oxygen, it just gets updated, added to menus, etc. It takes out the consciously remembering to update your oxygen install. ;-)
-James
On 24/09/15 17:35, Kevin Hawkins wrote:
According to http://wiki.tei-c.org/index.php/OXygen, the tei-oxygen Debian packages provides "automatic updates for new versions of the stylesheet library" (by which, I believe, we mean http://wiki.tei-c.org/index.php/Tei-xsl ). --Kevin
On 9/24/15 11:28 AM, Martin Holmes wrote:
Roberto's response is interesting; I've never really understood what the TEI Oxygen package does. Does anyone know? Does it simply provide a customized version of Oxygen that incorporates TEI stuff? If so, presumably it was obsoleted when the plugin was created.
Cheers, Martin
On 15-09-24 09:23 AM, James Cummings wrote:
On 24/09/15 17:14, Martin Holmes wrote:
Does it fail because it wants a password you don't have, or because your not SR and so you don't have access to his keys? Did you su rahtz?
I had 'su rahtz' before.
If we decide to take over building of the packages and move them, there's stuff that has to be done that I don't actually understand. Existing users, who are subscribed to the repo on the Oxford server, will need to remove that repo from their sources and substitute another one. I don't know how (assuming there is a way) to make that requirement known to package users, other than crude things like making the existing repository disappear so that they get errors when they do apt-get update and go off looking for answers. There's some research and learning to do here, so I think we need a little workgroup.
Yes, luckily, the type of person who is subscribed to the teideb repository is likely to be the type of person who won't mind switching the url to a new one. But yes... I think we need a decision on: - should we be maintaining debian packages? - if so, which packages? - where should it be located?
Meanwhile, I've asked a simple question on the TEI-L list. If it turns out no-one is using the packages at all, then we might consider abandoning them.
I use them but don't need to.
-James