.gramps

classic Classic list List threaded Threaded
32 messages Options
12
Reply | Threaded
Open this post in threaded view
|

.gramps

Peter Landgren
Devs,

Should gramps 4.1.0 and gramps master share the same gramps.ini file?

/Peter

--
Peter Landgren
Talken Hagen
671 94  Brunskog
0570-530 21
070-345 0964


------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

John Ralls-2

On Jun 4, 2014, at 7:23 AM, Peter Landgren wrote:

> Devs,
>
> Should gramps 4.1.0 and gramps master share the same gramps.ini file?

Right now it doesn't matter because master won't have diverged much. In the longer run, of course not; otherwise there can be no changes in master that would make the .ini file incompatible with gramps41.

Regards,
John Ralls


------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

Paul Franklin-5
In reply to this post by Peter Landgren
On 6/4/14, Peter Landgren <[hidden email]> wrote:
> Should gramps 4.1.0 and gramps master share the same gramps.ini file?

I have changed version.py in trunk/master to 4.2.0.

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

Paul Franklin-5
On 6/10/14, Paul Franklin <[hidden email]> wrote:
> On 6/4/14, Peter Landgren <[hidden email]> wrote:
>> Should gramps 4.1.0 and gramps master share the same gramps.ini file?
>
> I have changed version.py in trunk/master to 4.2.0.
>

I have reverted that change, back to 4.1.0, since there are
more things which are required and I don't have time now.

For instance changing every *.gpr.py file in gramps to also
have 4.2, as well as making a new branch in the addons
repository for the third-party plugins.

And as John said, it isn't very critical right now.  We all
have other things which are more urgent, I would guess.

FYI.

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

jerome
Devs,

Code keeps some "gramps version" references.
Most on urls for help or some warning messages.

I tried to limit this usage on master.
It is not perfect, like before, but it should avoid mixup with version numbers.

There is also a possible change which calls constant too:

eg, 
--- a/gramps/plugins/gramplet/gramplet.gpr.py
+++ b/gramps/plugins/gramplet/gramplet.gpr.py
@@ -29,6 +29,7 @@
 
 from gramps.gen.const import GRAMPS_LOCALE as glocale
 _ = glocale.translation.sgettext
+from gramps.version import major_version
 
 #------------------------------------------------------------------------
 #
@@ -40,7 +41,7 @@ register(GRAMPLET,
          name=_("Age on Date"), 
          description = _("Gramplet showing ages of living people on a specific date"),
          version="2.0.0",
- gramps_target_version="4.1",
+ gramps_target_version = major_version,
          status = STABLE,
          fname="ageondategramplet.py",
          height=200,
@@ -61,7 +62,7 @@ register(GRAMPLET,
          detached_width = 600,
          detached_height = 450,
          version="1.0.0",
- gramps_target_version="4.1",
+ gramps_target_version = major_version,
          )
 
 register(GRAMPLET, 
@@ -74,7 +75,7 @@ register(GRAMPLET,
          gramplet = 'CalendarGramplet',
          gramplet_title=_("Calendar"),
          version="1.0.0",
- gramps_target_version="4.1",
+ gramps_target_version = major_version,

etc ...

The problem is that this change will allow to run these plugins with all versions of gramps! So, this type of change might be useful for migration to a next major version, but it is also wrong on the way used. :(

Is there a quick solution for migrating gramps_target_version to "4.2"?


Jérôme.

Le mer. 11 juin 2014 at 19:43, Paul Franklin <[hidden email]> a écrit :
On 6/10/14, Paul Franklin <[hidden email]> wrote:
On 6/4/14, Peter Landgren <[hidden email]> wrote:
Should gramps 4.1.0 and gramps master share the same gramps.ini file?
I have changed version.py in trunk/master to 4.2.0.
I have reverted that change, back to 4.1.0, since there are more things which are required and I don't have time now. For instance changing every *.gpr.py file in gramps to also have 4.2, as well as making a new branch in the addons repository for the third-party plugins. And as John said, it isn't very critical right now. We all have other things which are more urgent, I would guess. FYI. ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ Gramps-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gramps-devel

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

Paul Franklin-5
On 6/16/14, Jerome <[hidden email]> wrote:

> Is there a quick solution for migrating gramps_target_version to "4.2"?

I will be happy to change version.py (from the 4.1.99 you made it)
to 4.2.0, and to change every trunk/master *.gpy.py file to say "4.2"
instead of the "4.1" they say now.

I can do it in am hour or two.  Is that "quick" enough?  8-)

I don't want to touch the gramps-addons repo however.
Somebody else will have to make a gramps41 branch there,
and update its trunk to 4.2 -- or whatever is needed there.


Also, earlier today you made this change in gramps/gui/grampsgui.py:

-            _("This Gramps 4.1-trunk is a development release. "
+            _("This Gramps master is a development release. "

and I suggest the second line should instead be something like:

+            _("This Gramps \('master'\) is a development release. "

with the single-quote marks around the "master" inside the parens.

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

John Ralls-2
In reply to this post by jerome

On 16 Jun 2014, at 08:07, Jerome <[hidden email]> wrote:

> Devs,
>
> Code keeps some "gramps version" references.
> Most on urls for help or some warning messages.
>
> I tried to limit this usage on master.
> It is not perfect, like before, but it should avoid mixup with version numbers.
>
> There is also a possible change which calls constant too:
>
> eg,
> --- a/gramps/plugins/gramplet/gramplet.gpr.py
> +++ b/gramps/plugins/gramplet/gramplet.gpr.py
> @@ -29,6 +29,7 @@
>  
>  from gramps.gen.const import GRAMPS_LOCALE as glocale
>  _ = glocale.translation.sgettext
> +from gramps.version import major_version
>  
>  #------------------------------------------------------------------------
>  #
> @@ -40,7 +41,7 @@ register(GRAMPLET,
>           name=_("Age on Date"),
>           description = _("Gramplet showing ages of living people on a specific date"),
>           version="2.0.0",
> - gramps_target_version="4.1",
> + gramps_target_version = major_version,
>           status = STABLE,
>           fname="ageondategramplet.py",
>           height=200,
> @@ -61,7 +62,7 @@ register(GRAMPLET,
>           detached_width = 600,
>           detached_height = 450,
>           version="1.0.0",
> - gramps_target_version="4.1",
> + gramps_target_version = major_version,
>           )
>  
>  register(GRAMPLET,
> @@ -74,7 +75,7 @@ register(GRAMPLET,
>           gramplet = 'CalendarGramplet',
>           gramplet_title=_("Calendar"),
>           version="1.0.0",
> - gramps_target_version="4.1",
> + gramps_target_version = major_version,
>
> etc ...
>
> The problem is that this change will allow to run these plugins with all versions of gramps! So, this type of change might be useful for migration to a next major version, but it is also wrong on the way used. :(
>
> Is there a quick solution for migrating gramps_target_version to "4.2"?

find contrib -name *.gpr.py -exec sed -i '' -e s/gramps_target_version=4.1/gramps_target_version=4.2/ {} \;

N.B that's two single quotes after the -i.

Regards,
John Ralls


------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

Nick Hall
In reply to this post by jerome
On 16/06/14 16:07, Jerome wrote:
> Is there a quick solution for migrating gramps_target_version to "4.2"?
>

  I would probably use sed to make the change to all gpr files.

Do you want me to make the change for you?

Nick.


------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

jerome
In reply to this post by Paul Franklin-5
> I don't want to touch the gramps-addons repo however.
> Somebody else will have to make a gramps41 branch there,
> and update its trunk to 4.2 -- or whatever is needed there.

This has been done some days ago! ;)

> I can do it in am hour or two. Is that "quick" enough? 8-)

I thought "at a glance".
No urgency.

John's command looks right!
Thanks!

> Also, earlier today you made this change in gramps/gui/grampsgui.py:

> - _("This Gramps 4.1-trunk is a development release. "
> + _("This Gramps master is a development release. "

> and I suggest the second line should instead be something like:

> + _("This Gramps \('master'\) is a development release. "

> with the single-quote marks around the "master" inside the parens.

Sounds good! Feel free to make the change.

My primary idea was only to avoid version number into the message.
True, as we change the translation string, maybe we can highlight "master" word too.

If everything works as expected, once we move to a new major version on trunk (and create a new gramps.ini for gramps42), we should see this warning message. So, on the first run only, like before (trunk/gramps41)!


Jérôme

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

jerome
In reply to this post by John Ralls-2
Thanks!

The first part works fine. 

eg,

$ find gramps/plugins/* -name *.gpr.py

but on the second part, sed cannot read these files under my config!


Regards,
Jérôme


Le lun. 16 juin 2014 at 18:21, John Ralls <[hidden email]> a écrit :
Is there a quick solution for migrating gramps_target_version to "4.2"?
find contrib -name *.gpr.py -exec sed -i '' -e s/gramps_target_version=4.1/gramps_target_version=4.2/ {} \; N.B that's two single quotes after the -i. Regards, John Ralls

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

John Ralls-2

On 16 Jun 2014, at 10:03, Jerome <[hidden email]> wrote:

> Thanks!
>
> The first part works fine.
>
> eg,
>
> $ find gramps/plugins/* -name *.gpr.py
>
> but on the second part, sed cannot read these files under my config!
>

What error message does it raise?

Regards,
John Ralls



------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

Paul Franklin-5
In reply to this post by jerome
On 6/16/14, Jerome <[hidden email]> wrote:
>  > + _("This Gramps \('master'\) is a development release. "
>
>  > with the single-quote marks around the "master" inside the parens.
>
> Sounds good! Feel free to make the change.

I have changed that line, in trunk/master only, to:

+ _("This Gramps ('master') is a development release. "

as the backslashes were not needed.

I will leave it to one of you to make the "4.2" changes.

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

jerome
In reply to this post by John Ralls-2
sed: impossible de lire : Aucun fichier ou dossier de ce type
=> sed: cannot read: No file or directory of this type

$ find gramps/plugins/* -name *.gpr.py -exec sed -e s/gramps_target_version=4.1/gramps_target_version=4.2/ {} \;

runs without error (it prints, no changes).

   It looks like related to:
       sed -i ''


Regards,
Jérôme


Le lun. 16 juin 2014 at 19:23, John Ralls <[hidden email]> a écrit :
On 16 Jun 2014, at 10:03, Jerome <[hidden email]> wrote:
Thanks! The first part works fine. eg, $ find gramps/plugins/* -name *.gpr.py but on the second part, sed cannot read these files under my config!
What error message does it raise? Regards, John Ralls

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

jerome
Should I put a $pwd somewhere on the command line?

Le lun. 16 juin 2014 at 20:03, Jerome <[hidden email]> a écrit :
sed: impossible de lire : Aucun fichier ou dossier de ce type
=> sed: cannot read: No file or directory of this type

$ find gramps/plugins/* -name *.gpr.py -exec sed -e s/gramps_target_version=4.1/gramps_target_version=4.2/ {} \;

runs without error (it prints, no changes).

   It looks like related to:
       sed -i ''


Regards,
Jérôme


Le lun. 16 juin 2014 at 19:23, John Ralls <[hidden email]> a écrit :
On 16 Jun 2014, at 10:03, Jerome <[hidden email]> wrote:
Thanks! The first part works fine. eg, $ find gramps/plugins/* -name *.gpr.py but on the second part, sed cannot read these files under my config!
What error message does it raise? Regards, John Ralls

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

John Ralls-2

On Jun 16, 2014, at 11:14 AM, Jerome <[hidden email]> wrote:

> Should I put a $pwd somewhere on the command line?
>
> Le lun. 16 juin 2014 at 20:03, Jerome <[hidden email]> a écrit :
>> sed: impossible de lire : Aucun fichier ou dossier de ce type
>> => sed: cannot read: No file or directory of this type
>>
>> $ find gramps/plugins/* -name *.gpr.py -exec sed -e s/gramps_target_version=4.1/gramps_target_version=4.2/ {} \;
>>
>> runs without error (it prints, no changes).
>>
>>    It looks like related to:
>>        sed -i ''

Yeah, sorry, on Linux there should be no space, so `sed -i’’ …`.

And the replacement string is gramps_target_version = ‘4.1’, so the working command is:
find gramps/plugins -name *.gpr.py -exec sed -i'' -e "s/gramps_target_version = '4.1'/gramps_target_version = '4.2'/" {} \;

That leaves gramps/plugins/view/geography.gpr.py, which defines MODULE_VERSION=“4.1”, but that’s just one line in one file, so it’s perhaps easier to hand-edit it.

Regards,
John Ralls
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

Paul Franklin-5
> And the replacement string is gramps_target_version = '4.1',

Ah yes, but the observant recursive grepper will have noticed
that some .gpr.py files have '4.1' and others have "4.1" (with the
two different types of quotation marks).

So maybe whoever does it might need to have a small shell
script, and not attempt to do it in one line, even if it doubtless
could technically be done in one?

Just a thought.

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

John Ralls-2

On 16 Jun 2014, at 13:42, Paul Franklin <[hidden email]> wrote:

>> And the replacement string is gramps_target_version = '4.1',
>
> Ah yes, but the observant recursive grepper will have noticed
> that some .gpr.py files have '4.1' and others have "4.1" (with the
> two different types of quotation marks).
>
> So maybe whoever does it might need to have a small shell
> script, and not attempt to do it in one line, even if it doubtless
> could technically be done in one?
>
> Just a thought.
[Oops, wrong from address.]
Don't know regular expressions well, I guess:

find gramps/plugins -name *.gpr.py -exec sed -i'' -e "s/gramps_target_version = ["']4.1["']/gramps_target_version = '4.2'/" {} \;

Regards,
John Ralls


------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

Paul Franklin-5
On 6/16/14, John Ralls <[hidden email]> wrote:
> Don't know regular expressions well, I guess:
>
> find gramps/plugins -name *.gpr.py -exec sed -i'' -e
> "s/gramps_target_version = ["']4.1["']/gramps_target_version = '4.2'/" {}
> \;

find gramps  -name *.gpr.py -exec sed -i'' -e
/gramps_target_version/s/4.1/4.2/ {} \;

You like to write long commands, I guess.

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

jerome
Ahh, both work fine. :)

  I am reassured ... we will be able to do this change, quickly!


Thanks!


Le mar. 17 juin 2014 at 9:04, Paul Franklin <[hidden email]> a écrit :
On 6/16/14, John Ralls <[hidden email]> wrote:
Don't know regular expressions well, I guess: find gramps/plugins -name *.gpr.py -exec sed -i'' -e "s/gramps_target_version = ["']4.1["']/gramps_target_version = '4.2'/" {} \;
find gramps -name *.gpr.py -exec sed -i'' -e /gramps_target_version/s/4.1/4.2/ {} \; ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ Gramps-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gramps-devel

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
Reply | Threaded
Open this post in threaded view
|

Re: .gramps

Paul Franklin-5
>   I am reassured ... we will be able to do this change, quickly!

Don't forget to change the geography.gpr.py that John found.

Personally, if it were me, I would change it to be like every
other gpr.py file, with an explicit "4.2" in every line, and get
rid of that constant, so we don't have to remember to do a
special-case change to that file on every major release.

But you are the release manager.  Maybe your memory is
better than mine!  8-)

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Gramps-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-devel
12