Spell Deprecation

Can someone please outline the proper procedure to deprecate spells
(and possibly post it on the wiki)?

>From my understanding (by examining previous spells), you completely
remove the spell if there is no direct replacement for it.
If there is, you add an up_trigger to cast its replacement and an
up_trigger to dispel_self, replace the contents of PRE_BUILD, BUILD,
and INSTALL with true, comment out the SOURCE info in DETAILS, and
remove any remaining files (other than HISTORY). Is that correct?

In case anyone is wondering, I want to deprecate howl (it currently
fails to build and is long dead) and replace any current depends on it
with -sub COMPAT_HOWL avahi.

Re: SPELL > SCRIPT

Am Thu, 24 May 2012 21:19:10 +1200
schrieb AbH Belxjander Draconis Serechai <belxjander <at> gmail.com>: 

> wholesale replacement using a grep?

Something along that, yes. Though, naturally, I'd do something along

	perl -pi -e 's:\$\{SCRIPT_DIRECTORY\}:\${SPELL_DIRECTORY}:g;
s:\$SCRIPT_DIRECTORY:\$SPELL_DIRECTORY:g;'  $spell_file

others would use sed ... but, well, that is not the point: The point is whether we should start an argument
about ${varname} vs. $varname

Alrighty then,

Thomas

_______________________________________________
SM-Discuss mailing list
SM-Discuss <at> lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/sm-discuss

Re: Announcing stable-rc-0.61 (20120517) chroot image release

On Wed, 23 May 2012 09:41:47 +1200
AbH Belxjander Draconis Serechai <belxjander <at> gmail.com> wrote:

> any chance of a cross-compiler setup being built as an "expanded" chroot image?

that's an interesting idea, but I'm not sure all the spells are pretty
ready for cross-compilation.

though I track T2 project [0], which has _A LOT_ of work on this done.
And it's aimed on providing clear packages built from source without
any extra patches, only those needed for cross-compile.

[0] http://www.t2-project.org/about.html

> 
> I've managed to break my own system in trying to setup such a thing a
> couple of times now and would certainly appreciate help in getting a
> PPC build update happening.
> 
> Belxjander
> 
> On Wed, May 23, 2012 at 9:36 AM, Vlad Glagolev <stealth <at> sourcemage.org> wrote:
> >> No, they cannot be used for producing ISOs
> >
> > then you seem misunderstanding me for the 3rd time as I do for you :)
> >
> >> The images
> >
> > I didn't mean the images themselves, but theirs contents.
> > it can be even just a spell-list taken from it.

SPELL > SCRIPT

For all the spellwriters,

even while $SCRIPT_DIRECTORY and $SPELL_DIRECTORY are equal in
functionality, please use the last one as it actually makes more sense.

--

-- 
Dont wait to die to find paradise...
--
Cheerz,
Vlad "Stealth" Glagolev

_______________________________________________
SM-Discuss mailing list
SM-Discuss <at> lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/sm-discuss

stable-rc-0.61 REcut and ready for testing (dub 2)

Hi everyone,

stable-rc 0.61 is REcut and ready for testing again.

Since we have new up-to-date chroot images now, the process of testing
an upgrade from 0.60 to 0.61 should go smoothly.

The release target is *June 15th*. It will take a bit more time than
usually, cause we had a notable pause from previous stable release.

The tarballs have been signed and uploaded to our server and will be
propogating out to the mirrors within six hours.

To download the grimoire manually, get
http://codex.sourcemage.org/stable-rc.tar.bz2 or specifically
http://codex.sourcemage.org/stable-rc-0.61.tar.bz2 .

GPG signatures are available at
http://codex.sourcemage.org/stable-rc.tar.bz2.asc or
http://codex.sourcemage.org/stable-rc-0.61.tar.bz2.asc .

As always don't forget to file any bugs against our issue tracker[0] so
we can resolve them and integrate the fixes before release. New version
'0.61-rc' is still there, so use it when submitting the bugs.

Let's give this new stable-rc a good testing!

[0] http://www.sourcemage.org/projects/grimoire/issues

--

-- 

general comment

_______________________________________________
SM-Discuss mailing list
SM-Discuss <at> lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/sm-discuss

patches

I have a patch to a spell. The patch size is ~ 10k bytes, 200 lines

Is it better to compress the patch or not?
If it is not compressed, git can do a better job of reducing space usage.
Thoughts?

Treeve

util-linux 2.21 and inittab update in FINAL

Hi,

I just got bitten by an util-linux update breaking my login. Seems like this is
http://www.sourcemage.org/issues/110 and there is code in FINAL dealing with this:

if [ "${VERSION:0:4}" == "2.20" ] && [ "${OLD_SPELL_VERSION:0:4}" == "2.19" ]; then
  message "New version of util-linux needs to update /etc/inittab ..." &&
  cp $INSTALL_ROOT/etc/inittab $INSTALL_ROOT/etc/inittab-$(date +'%Y%m%d%H%M') &&
  sed -i "s:/dev/tty:tty:" $INSTALL_ROOT/etc/inittab &&
  message "Updated"
fi &&

Now, of course I broke this by doing the update too late, jumping from 2.19 to 2.21. So I have two questions
about this:

1. Was the intention to delete the FINAL code when updating to 2.21? Because now it is dead meat right there.
2. I don't really like the sed line there ... it doesn't check if there is actually agetty in the line it works
on. There are other getty programs.

So ... what's the intention here? Just remove the code as the update to 2.20 is history?

Alrighty then,

Thomas

PS: I want to add that I really, really am angry at util-linux folks for not just supporting /dev paths
anyway. What's so hard about this?

_______________________________________________
SM-Discuss mailing list
SM-Discuss <at> lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/sm-discuss

[PATCH] Fix Atom specs clash

Signed-off-by: Ismael Luceno <ismael.luceno <at> gmail.com>
---
 32/ia32/intel/x86/atom                  |    4 ++--
 64/x86_64/intel/em64t/{atom => atom_64} |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
 rename 64/x86_64/intel/em64t/{atom => atom_64} (80%)

diff --git a/32/ia32/intel/x86/atom b/32/ia32/intel/x86/atom
index 86f6e26..054a669 100755
--- a/32/ia32/intel/x86/atom
+++ b/32/ia32/intel/x86/atom
@@ -1,8 +1,8 @@
-CPUNAME="Intel Atom"
+CPUNAME="Intel Atom, 32bit mode"
 if use_gcc2; then
   CFLAGS="-march=i686"
 else
-  CFLAGS="-march=atom"
+  CFLAGS="-march=atom -m32"
 fi
 HOST="i686-pc-linux-gnu"
 FAST="-O3"
diff --git a/64/x86_64/intel/em64t/atom b/64/x86_64/intel/em64t/atom_64
similarity index 80%
rename from 64/x86_64/intel/em64t/atom
rename to 64/x86_64/intel/em64t/atom_64
index d53e16b..247fc4a 100755
--- a/64/x86_64/intel/em64t/atom
+++ b/64/x86_64/intel/em64t/atom_64
@@ -3,7 +3,7 @@ CPUNAME="Intel Atom 64bit (all except Z5xx, Z6xx and N2xx)"
 if use_gcc2 ; then
   CFLAGS="-march=i686"
 else
-  CFLAGS="-march=atom -fPIC -DPIC"
+  CFLAGS="-march=atom -m64 -fPIC -DPIC"
 fi

 HOST="x86_64-pc-linux-gnu"
--

-- 
1.7.9.4

Grimoire Lead vote

According to [1], we're supposed to have a vote for the Grimoire Lead in
March. As it's now mid-March, I'm going to try to get the ball rolling
by placing some nominations.

I hereby nominate the following mages:

Andraž 'ruskie' Levstik
Vlag 'Stealth' Glagolev
Arjan 'abouter' Bouter

1: http://wiki.sourcemage.org/SourceMage/Voting_Policy

--

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

_______________________________________________
SM-Discuss mailing list
SM-Discuss <at> lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/sm-discuss

z-rejected push failing

Looks like I can't push to the z-rejected repo. I've never pushed
to this repo before, so probably it's just a permission issue.

Can I get access, please? *_*

_______________________________________________
SM-Discuss mailing list
SM-Discuss <at> lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/sm-discuss