Friday, November 30, 2018

Re: get production/tryton out of attic (aka reimporting it)

On Thu, Nov 29, 2018 at 12:59:59PM +0100, Antoine Jacoutot wrote:
> I think the best move is that I import your work and we will enable it as a
> second step when we are 100% certain everything is good.
> Sounds like a plan?

import the whole stuff and working in tree ? it could be possible. I
would just need to keep a production/tryton/5.0/Makefile clean enough to
ensure only finalized ports are linked in tree.

I will work on having my WIP tree on a clean state (like removing my
tryton/4.8 branch who were here only for testing @option branch stuff)
and I will come back for having formal OK for inclusion.

Thanks.
--
Sebastien Marie

> On Thu, Nov 29, 2018 at 11:22:11AM +0100, Sebastien Marie wrote:
> > Hi,
> >
> > I would like to get productivity/tryton out of Attic, and take the
> > maintainership of it. Disclamer: I am using it.
> >
> > It has been initially removed (on May 8 2017) when I discussed with
> > aja@ about updating the super-old-version we had, and he saw it was not
> > really useful to maintain it (and import several new python ports) if
> > nobody really uses it (at this time I was interested in looking at it
> > only).
> >
> > Mon May 8 17:01:14 2017 UTC
> >
> > Delete tryton; the version we have in ports is not really maintained. I started
> > to work on an diff to update everything to the latest release just to realise
> > that there wasn't a point in doing this it's essentially a matter of
> > ftp+tar xzf. Not worth maintaining 100+ packages.
> >
> > I disagree a bit about the "ftp+tar zxf" part of the comment. If
> > it could apply to some parts of Tryton, I think it doesn't for all
> > compoments.
> >
> >
> > For reimporting it, I would like to take a different approch.
> >
> > First it would be important to have the possibility to have multiple
> > versions in the tree. For now, I would like to import only the
> > latest stable version (5.0), which is LTS (support from 10/2018 to
> > 10/2023). And next, import versions when released (and remove them when
> > not supported any more).
> >
> > It is important as people using Tryton could want to stick on some LTS
> > version as long it is supported whereas some others will want to follow
> > latest stable version ("minor" releases are maintained for 1 year).
> >
> > So it means at anytime we shouldn't have more than 3-4 differentes
> > versions of tryton.
> >
> > I use branch option (to have multiple versions of tryton) and make the
> > versions mutually-exclusive (you couldn't install trytond-5.0 with some
> > modules for 5.1 for example).
> >
> >
> > Next, I plan to reimport in priority:
> > - trytond : the server
> > - tryton : gtk desktop client
> > - sao : web client
> > - proteus : library to access Tryton models like a client
> >
> > it is the important part to have as trytond has to be properly
> > integrated to the system (_trytond user, rc.d scripts, ...)
> >
> > and after that, if people agree, the official tryton modules (~ 130
> > differents modules). Technically, the modules could be installed from
> > outside the port tree. But it could be a good thing to have, at least,
> > some of them in order to make evident the use of some others python
> > modules.
> >
> > For example, we have the following ports in tree because of some tryton
> > modules: devel/py-simpleeval, textproc/py-ofxparse, devel/py-simplesoap
> > (proposed on ports@, but not imported for now). Having the related
> > tryton modules in ports tree too would make more evident the use of
> > these python ports.
> >
> > But as long I have the four main compoments, I could live without
> > the others tryton modules (which could enter in the "ftp+tar xzf"
> > previous description). In fact, for any production use of Tryton, the
> > user will have locally installed tryton modules (eventually home-made)
> > for customization. So the official tryton modules could be manually
> > installed too.
> >
> >
> > I could be noted that since the 5.0 version of Tryton, all compoments of tryton are
> > py3-only. So it simplify a bit the maintenance.
> >
> >
> > I am maintaining a WIP tree at
> > https://bitbucket.org/semarie/tryton-ports/src/ . Not all modules has been
> > included for now, as I am adding them when there are properly tested.
> >
> >
> > The following files are attached:
> > - devel/quirks change to remove the fact that 'tryton' and 'trytond' has
> > been removed.
> >
> > - infrastructure/db/user.list change to ressurect uid 675 (I changed the
> > name from _tryton to _trytond. is it a problem ?)
> >
> > - tarball for productivity/tryton with trytond, tryton, sao, and proteus
> > + 2 modules used for in the 'test' target of proteus
> >
> > I have a somehow long README in trytond (direct reading at
> > https://bitbucket.org/semarie/tryton-ports/src/default/5.0/trytond/pkg/README)
> > to document installation and configuration. I think it is self
> > explaining why I think this part is more than just "ftp+tar xzf".
> >
> > Comments or OK ?
> >
> > Thanks.
> > --
> > Sebastien Marie
>
> > Index: files/Quirks.pm
> > ===================================================================
> > RCS file: /cvs/ports/devel/quirks/files/Quirks.pm,v
> > retrieving revision 1.665
> > diff -u -p -r1.665 Quirks.pm
> > --- files/Quirks.pm 27 Nov 2018 15:24:15 -0000 1.665
> > +++ files/Quirks.pm 29 Nov 2018 08:24:00 -0000
> > @@ -830,8 +830,6 @@ my $obsolete_reason = {
> > 'xgrab' => 9,
> > 'quirc' => 3,
> > 'xspread' => 3,
> > - 'tryton' => 1,
> > - 'trytond' => 1,
> > 'sharity-light' => 6,
> > 'py-axiom' => 5,
> > 'py-epsilon' => 5,
>
> > Index: infrastructure/db/user.list
> > ===================================================================
> > RCS file: /cvs/ports/infrastructure/db/user.list,v
> > retrieving revision 1.330
> > diff -u -p -r1.330 user.list
> > --- infrastructure/db/user.list 29 Nov 2018 00:38:14 -0000 1.330
> > +++ infrastructure/db/user.list 29 Nov 2018 08:22:57 -0000
> > @@ -183,7 +183,7 @@ id user group port options
> > 672 _radicale _radicale productivity/radicale
> > 673 _buildbot _buildbot devel/py-buildbot
> > 674 _buildslave _buildslave devel/py-buildslave
> > -#675 _tryton _tryton productivity/tryton/trytond
> > +675 _trytond _trytond productivity/tryton
> > 676 _gdm _gdm x11/gnome/gdm
> > 677 _scamper _scamper net/scamper
> > 678 _owampd _owampd net/owamp
>

No comments:

Post a Comment