Skip to Content.
Sympa Menu

sm-discuss - [SM-Discuss] Code reuse / Guidelines

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Elisamuel Resto <samuel AT dragonboricua.net>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: [SM-Discuss] Code reuse / Guidelines
  • Date: Thu, 17 Jan 2008 10:45:43 -0400

On Thu, 17 Jan 2008 00:06:45 +0500, Alexander Tsamutali wrote:
> В Wed, 16 Jan 2008 16:36:50 +0300
> Vlad Glagolev <stealth AT sourcemage.org> пишет:
> > On Wed, 16 Jan 2008 09:22:39 -0400
> > Elisamuel Resto <samuel AT dragonboricua.net> wrote:
> > > On Wed, 16 Jan 2008 02:18:08 -0600, Vlad Glagolev wrote:
> > > > GIT changes to master grimoire by Vlad Glagolev
</snip>
> > >
> > > Just because it's written in Python it means it should not go in
> > > audio-players? How come?
> > >
> >
> > Well, less code reuse/useless functions.. everything python-related
> > goes into python, perl-related goes into perl, lua-, ruby-, haskell-,
> > etc- related goes into theirs dirs. Look at the ruskie's commits for
> > example about such things as ruby-gtk (yes, it's not in x11-libs
> > anymore).
>
> Sorry, I can't understand this.
>
> When I think about sonata, i think "mpd
> client, audio player". As a user who looks on two sections:
> audio-players and python-pypi I would expect to find sonata in
> audio-players section, IOW they expect to find relevant software there.
> If you say that CODE REUSE is the most important thing, then we should
> hide such thing as "sections" from user because users DON'T CARE about
> our CODE REUSE.
>
> When I created haskell section none said nothing about
> CODE REUSE [0], so what happened now? Someone created new grimoire
> standards? Where can I read them?
>
> P.S. IMHO Source Mage will continue to suck and I will continue whining
> [1] time to time, and after some time I'll move to Arch.
>
> [0] https://lists.ibiblio.org/sympa/arc/sm-discuss/2007-August/017167.html
> [1] https://lists.ibiblio.org/sympa/arc/sm-discuss/2007-January/015956.html

I agree with your comment about the sections being logical to the user. But
the fact
of the matter is, while the user doesn't *care* about it, *we* do since we
maintain
these spells. If one updates the python build functions, we would need to also
update any and all spells outside of the section to accomodate... now who is
making
double workload?

There are no set standards, but sensible guidelines on what you should do...
if you
asked.

The thread you referenced to which I saw briefly last year was well
discussed, you
shuld see the ideas/thoughts of most of our *active* developers back then and
I
assume those have not changed.

--
Elisamuel Resto <samuel AT dragonboricua.net>
Source Mage GNU/Linux / http://www.sourcemage.org
ID: 0x18615F19 / FP: B66D 1C2A E8EE B922 1D9C D98F D2D5 FB61 1861 5F19

Attachment: signature.asc
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page