Smalltalk › Pharo › Pharo Smalltalk Developers

CodeImporter and Rubric will not be external projects managed by configurations

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Pavel Krivanek-3

CodeImporter and Rubric will not be external projects managed by configurations

Hi,

to make our and your lifes easier we want to stop to manage CodeImporter and Rubric as external projects. For CodeImporter it makes no sense to have it as external project and moreover why to have special configuration for only one package. The Rubric has a lot of small updates, not defined maintainer and manage it externally is a pain for everyone.

Let us know if you have something against it.

Cheers,

-- Pavel

Sven Van Caekenberghe-2

Re: CodeImporter and Rubric will not be external projects managed by configurations

Yes, good idea, external projects only make sense if they really can exist outside Pharo and if they are actively maintained as such.

> On 10 Jun 2016, at 10:43, Pavel Krivanek <[hidden email]> wrote:
>
> Hi,
>
> to make our and your lifes easier we want to stop to manage CodeImporter and Rubric as external projects. For CodeImporter it makes no sense to have it as external project and moreover why to have special configuration for only one package. The Rubric has a lot of small updates, not defined maintainer and manage it externally is a pain for everyone.
>
> Let us know if you have something against it.
>
> Cheers,
> -- Pavel

Nicolai Hess-3-2

Re: CodeImporter and Rubric will not be external projects managed by configurations

I don't much about code importer, but
+1 for rubric

2016-06-10 10:50 GMT+02:00 Sven Van Caekenberghe <[hidden email]>:

Yes, good idea, external projects only make sense if they really can exist outside Pharo and if they are actively maintained as such.

> On 10 Jun 2016, at 10:43, Pavel Krivanek <[hidden email]> wrote:
>
> Hi,
>
> to make our and your lifes easier we want to stop to manage CodeImporter and Rubric as external projects. For CodeImporter it makes no sense to have it as external project and moreover why to have special configuration for only one package. The Rubric has a lot of small updates, not defined maintainer and manage it externally is a pain for everyone.
>
> Let us know if you have something against it.
>
> Cheers,
> -- Pavel

stepharo

Re: CodeImporter and Rubric will not be external projects managed by configurations

In reply to this post by Sven Van Caekenberghe-2

Cargo all the packages have a configuration and it should be easier.
even if projects will have to specify their hosts.

BTW I hope that we will kill rubric because alain did it just as a hack
to help synectique.

> Yes, good idea, external projects only make sense if they really can exist outside Pharo and if they are actively maintained as such.
>
>> On 10 Jun 2016, at 10:43, Pavel Krivanek <[hidden email]> wrote:
>>
>> Hi,
>>
>> to make our and your lifes easier we want to stop to manage CodeImporter and Rubric as external projects. For CodeImporter it makes no sense to have it as external project and moreover why to have special configuration for only one package. The Rubric has a lot of small updates, not defined maintainer and manage it externally is a pain for everyone.
>>
>> Let us know if you have something against it.
>>
>> Cheers,
>> -- Pavel
>
>

Uko2

Re: CodeImporter and Rubric will not be external projects managed by configurations

On 11 Jun 2016, at 10:46, stepharo <[hidden email]> wrote:

Cargo all the packages have a configuration

Would work the same as having only one package per repo :)