Pharo 6.1 / 7, 0 Glorp smalltalkhub to github migration

Hi Everyone,

I've migrated Glorp v130, including GlorpSQLite, from smalltalkhub to
github using Peter Uhnak's excellent git-migration tool, see:
https://github.com/akgrant43/Glorp

To load Glorp:

Metacello new
    repository: 'github://akgrant43/Glorp/src';
    baseline: 'Glorp';
    load.


To load Glorp with the UDBC SQLite drivers:

Metacello new
    repository: 'github://akgrant43/Glorp/src';
    baseline: 'GlorpSQLite';
    load.


I'm not familiar with the other drivers, so I'm happy to help, but would
like some assistance before migrating the other drivers.

If I don't hear any complaints in the next week I'll eventually get
around to modifying the ConfigurationOfGlorp on smalltalkhub to use the
github version for Pharo 6.1 and 7.0.  Older versions of Pharo will
continue to load Glorp from smalltalkhub.

If there's an official account that should own this project, I'm more
than happy to hand it over.

Cheers,
Alistair

hi, 

On 11 December 2017 at 14:13, Esteban Lorenzano <[hidden email]> wrote:
> hi,
>
> this migration was already made to:
>
> https://github.com/pharo-rdbms
>
> don’t you prefer to join that team and contribute to enhance there?

Aaarrrgghh!!!  I didn't know this existed!

I had a look through my email archive and couldn't find any reference to
it (pharo-user, pharo-dev and glorp-group).  Was it announced somewhere?


1. pharo-rdbms loses all the commit history of Glorp, while my version
keeps it all.

Would you prefer to keep the history, or don't think it matters?  If you
want to keep the history I'm happy to put in the effort to move it
across to pharo-rdbms.


2. I have write permissions for smalltalkhub/DBXtalk.  Is it possible to
get commit permission to pharo-rdbms?



3. Is there a reason why ConfigurationOfGlorp on smalltalkhub hasn't
been updated to use pharo-rdbms (or raise an error pointing to
pharo-rdbms)?


Thanks!
Alistair

EstebanLM wrote
> this migration was already made…

From http://smalltalkhub.com/#!/~DBXTalk/Glorp? If so, it would be great to
put a highly visible note there. I get so confused by mcz to git migrations,
even for my own projects, that I'm often tempted to delete the original repo
even though I know that's terrible form. I wish there was a flag in the
StHub model, but a note is better than nothing to prevent unnecessary work
as here.



-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

On 12 December 2017 at 02:24, Sean P. DeNigris <[hidden email]> wrote:
> EstebanLM wrote
>> this migration was already made…
>
> From http://smalltalkhub.com/#!/~DBXTalk/Glorp? If so, it would be great to
> put a highly visible note there. I get so confused by mcz to git migrations,
> even for my own projects, that I'm often tempted to delete the original repo
> even though I know that's terrible form. I wish there was a flag in the
> StHub model, but a note is better than nothing to prevent unnecessary work
> as here.

+1

This is what bit me as well (although it would have been better if I
had searched github as well).

Unless someone suggests a better idea, I think I'll also modify the
ConfigurationOfGlorp on smalltalkhub to raise a deprecation warning
for Pharo 7.0 redirecting users to the new repository.

Cheers,
Alistair

yes, I remember Guille sent a mail.

>
> 1. pharo-rdbms loses all the commit history of Glorp, while my version
> keeps it all.
>
> Would you prefer to keep the history, or don't think it matters?  If you
> want to keep the history I'm happy to put in the effort to move it
> across to pharo-rdbms.


of course this is better, but essentially we do not care much.
There is a huge impedance between git repositories and mcz files so we just preferred to put it there like that.
If you want to take the effort of moving to it, it will be fine :)

>
>
> 2. I have write permissions for smalltalkhub/DBXtalk.  Is it possible to
> get commit permission to pharo-rdbms?


done :)

>
>
> 3. Is there a reason why ConfigurationOfGlorp on smalltalkhub hasn't
> been updated to use pharo-rdbms (or raise an error pointing to
> pharo-rdbms)?

not really, just lack of time.

Esteban

>
>
> Thanks!
> Alistair
>

Hi Esteban,

On 12 December 2017 at 14:02, Esteban Lorenzano <[hidden email]> wrote:
OK.  I should have checked on github anyway.


At the moment it looks like I can't create a new repository (see below).


>> 2. I have write permissions for smalltalkhub/DBXtalk.  Is it possible to
>> get commit permission to pharo-rdbms?
>
>
> done :)

Thanks!

I'm not familiar with github privileges, so my apologies in advance if
I'm confused.

I can see that I'm a team member, but it looks like I don't have write
privilege, e.g. if I try to create a development branch and push it:

$ git push --set-upstream origin development
ERROR: Permission to pharo-rdbms/glorp.git denied to akgrant43.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


Also, trying to edit the readme from the github website has a "Propose
the change", rather than a "Commit changes" button.

Based on https://help.github.com/articles/repository-permission-levels-for-an-organization/
if I'm going to load the history, which I'd do by creating a new
repository, then I'd also need Admin rights (I'm fine if you don't
want to grant this, I'll just stick to the existing repository).




>> 3. Is there a reason why ConfigurationOfGlorp on smalltalkhub hasn't
>> been updated to use pharo-rdbms (or raise an error pointing to
>> pharo-rdbms)?
>
> not really, just lack of time.

OK.  After I've updated the repository I'll add a deprecation warning
in ConfigurationOfGlorp.


Thanks!
Alistair