Public SourceMage Discussion List

[flux <flux AT sourcemage.org>]

<snip>
> > > 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).
</snip>
> 
> 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

I'm not sure if this is a good idea, but what if the code for the spells
was kept in python-pypi to reduce code duplication, but a dir in
audio-players was symlinked to the spell dir in python-pypi? This would
enable the user to see the spell as present in audio-players, but allow
us to devel it where it belongs for dev purposes. Of course, this could
end up exploding into tons of symlinked dirs all over the place, but I'm
wondering what everyone's thoughts on this are. I guess it would be like
tagging, where stuff is supposed to get multiple tags.

-- 
Justin "flux" Boffemmyer
Cauldron wizard and general mage
Source Mage GNU/Linux
http://www.sourcemage.org

Attachment: pgpKbpfIxvbHR.pgp
Description: PGP signature