Smalltalk › Pharo › Pharo Smalltalk Users

Iceberg and resource files

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

kmo

Iceberg and resource files

I don't understand how iceberg handles resource files that you might also
like to version along with the pharo code.

Say I have an CSV file and a text file that my pharo application uses. How
do I include these in the iceberg commit/push? How do I see changes made in
these files from version to version?

Does iceberg only handle pharo code? Generally git clients don't care about
the file type - and it it is any kind of text you can see the actual
differences between each commit.

Ken

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

Stephane Ducasse-3

Re: Iceberg and resource files

You can version such code in your repo using git.
Now Iceberg does not manage them (from what I understood).
We will probably have a kind of GitRepo file Location so that you can
know from where you want to load such files. (Right now pointing to
"IceRepository default" should work).

Stef

On Sat, Jan 27, 2018 at 3:38 PM, kmo <[hidden email]> wrote:

> I don't understand how iceberg handles resource files that you might also
> like to version along with the pharo code.
>
> Say I have an CSV file and a text file that my pharo application uses. How
> do I include these in the iceberg commit/push? How do I see changes made in
> these files from version to version?
>
> Does iceberg only handle pharo code? Generally git clients don't care about
> the file type - and it it is any kind of text you can see the actual
> differences between each commit.
>
> Ken
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>

kmo

Re: Iceberg and resource files

OK. I thought that this was more or less the case. Thanks.

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

hernanmd

Re: Iceberg and resource files

In reply to this post by kmo

Hi Ken,

Some days ago I published a package to manage download of resources
from Metacello configurations.
Have a look at https://github.com/hernanmd/MetacelloFileDownload

Hernán

2018-01-27 11:38 GMT-03:00 kmo <[hidden email]>:

Peter Uhnak

Re: Iceberg and resource files

Hi,

> How do I include these in the iceberg commit/push?

> How do I see changes made in these files from version to version?

Apart from directly using the actual git repo outside of pharo, you can use the facade provided by IceRepository, or you can use libgit inside Pharo.

E.g. to add an external file to index (which will be then committed together with new code)

repo := IceRepository registry detect: [ :each | each name = 'some-repo' ].

repo addFilesToIndex: {'README.md'}.

Peter

On Sun, Jan 28, 2018 at 6:23 AM, Hernán Morales Durand <[hidden email]> wrote:

Hi Ken,

Some days ago I published a package to manage download of resources
from Metacello configurations.
Have a look at https://github.com/hernanmd/MetacelloFileDownload

Hernán

2018-01-27 11:38 GMT-03:00 kmo <[hidden email]>:
> I don't understand how iceberg handles resource files that you might also
> like to version along with the pharo code.
>
> Say I have an CSV file and a text file that my pharo application uses. How
> do I include these in the iceberg commit/push? How do I see changes made in
> these files from version to version?
>
> Does iceberg only handle pharo code? Generally git clients don't care about
> the file type - and it it is any kind of text you can see the actual
> differences between each commit.
>
> Ken
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>

kmo

Re: Iceberg and resource files

These suggestions look really good. Thanks to everyone.

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

demarey

Re: Iceberg and resource files

In reply to this post by kmo

Hi Ken,

> Le 27 janv. 2018 à 15:38, kmo <[hidden email]> a écrit :
>
> I don't understand how iceberg handles resource files that you might also
> like to version along with the pharo code.

For now, Iceberg do not really handle these files but it is planned in a next future.

> Say I have an CSV file and a text file that my pharo application uses. How
> do I include these in the iceberg commit/push? How do I see changes made in
> these files from version to version?

Currently, you cannot do anything related to this through the UI.
What you could do is to call directly Iceberg API to commit ressources to the git repository:
1/ write the resource content in git working copy (std file system). There is a utility method: IceRepository>>#saveContent: aString inWorkingCopyFile: aRelativePathString
2/ add these files to git index through: IceRepository>>addFilesToIndex: aListOfPaths
3/ commit :
iceRepository
commitIndexWithMessage: commitMessage
andParents: { iceRepository headCommit }

You can also read ressources by suing IceRepository>>#contentOfFileNamed: aPathString commit: aCommitId

Christophe.

> Does iceberg only handle pharo code? Generally git clients don't care about
> the file type - and it it is any kind of text you can see the actual
> differences between each commit.
>
> Ken
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>

Stephane Ducasse-3

Re: Iceberg and resource files

Guille shows me a filesystem git accessed and browsed from Pharo. Soon
to be public.

On Mon, Jan 29, 2018 at 10:14 AM, Christophe Demarey
<[hidden email]> wrote:

> Hi Ken,
>
>> Le 27 janv. 2018 à 15:38, kmo <[hidden email]> a écrit :
>>
>> I don't understand how iceberg handles resource files that you might also
>> like to version along with the pharo code.
>
> For now, Iceberg do not really handle these files but it is planned in a next future.
>
>> Say I have an CSV file and a text file that my pharo application uses. How
>> do I include these in the iceberg commit/push? How do I see changes made in
>> these files from version to version?
>
> Currently, you cannot do anything related to this through the UI.
> What you could do is to call directly Iceberg API to commit ressources to the git repository:
> 1/ write the resource content in git working copy (std file system). There is a utility method: IceRepository>>#saveContent: aString inWorkingCopyFile: aRelativePathString
> 2/ add these files to git index through: IceRepository>>addFilesToIndex: aListOfPaths
> 3/ commit :
> iceRepository
> commitIndexWithMessage: commitMessage
> andParents: { iceRepository headCommit }
>
> You can also read ressources by suing IceRepository>>#contentOfFileNamed: aPathString commit: aCommitId
>
> Christophe.
>
>> Does iceberg only handle pharo code? Generally git clients don't care about
>> the file type - and it it is any kind of text you can see the actual
>> differences between each commit.
>>
>> Ken
>>
>>
>>
>> --
>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>
>
>