SLUT distibution mangled?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Ido Yehieli

    #1

    SLUT distibution mangled?

    Hi,
    I was trying to download and install the latest SLUT (0.9.0) from

    and it seems both the zip and the tar.gz files are corrupted - the
    directory "aux" and the files within can not be extracted (using
    windows BTW). This happened with both the zip _and_ the tar.gz file.
    The strange thing is: even when I'm trying to create a directory 'aux'
    by myself it is not possible!
    Anyone here ever encountered this problem?

    Thank you in advance,
    Ido Yehieli.

  • Ido Yehieli

    #2
    Re: SLUT distibution mangled?

    OKl, sorry this seems to have nothing to do with SLUT it self, for some
    reason a directory names 'aux' can not be created... most bizzare.
    "mkdir aux" just returns "The directory name is invalid."

    Comment

    • Fredrik Lundh

      #3
      Re: SLUT distibution mangled?

      Ido Yehieli wrote:
      [color=blue]
      > OKl, sorry this seems to have nothing to do with SLUT it self, for some
      > reason a directory names 'aux' can not be created... most bizzare.
      > "mkdir aux" just returns "The directory name is invalid."[/color]

      on windows ?

      win32 reserves the file names CON, PRN, AUX, CLOCK$, NUL, COM1,
      COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2,
      LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9 for devices.

      </F>



      Comment

      • Ido Yehieli

        #4
        Re: SLUT distibution mangled?

        So I can't run SLUT on windows then?

        Comment

        • Paul McGuire

          #5
          Re: SLUT distibution mangled?

          "Ido Yehieli" <Ido.Yehieli@gm ail.com> wrote in message
          news:1138487092 .992012.217660@ f14g2000cwb.goo glegroups.com.. .[color=blue]
          > So I can't run SLUT on windows then?
          >[/color]
          Well, here's what I did (I'm running on WinXP).

          1. Opened up slut.zip with a text editor (used Scite.exe), and changed all
          of the "/aux" references to "/bux"
          2. Expanded the ZIP file.
          3. Renamed /bux folder to /auxx (/aux is not allowed)

          It turns out the this folder only contains a separate GIF builder utility,
          so I think this is not a critical part of the software.

          -- Paul


          Comment

          • Paul McGuire

            #6
            Re: SLUT distibution mangled?

            "Paul McGuire" <ptmcg@austin.r r._bogus_.com> wrote in message
            news:UwTCf.6784 $jO.4796@tornad o.texas.rr.com. ..[color=blue]
            > "Ido Yehieli" <Ido.Yehieli@gm ail.com> wrote in message
            > news:1138487092 .992012.217660@ f14g2000cwb.goo glegroups.com.. .[color=green]
            > > So I can't run SLUT on windows then?
            > >[/color]
            > Well, here's what I did (I'm running on WinXP).
            >
            > 1. Opened up slut.zip with a text editor (used Scite.exe), and changed all
            > of the "/aux" references to "/bux"
            > 2. Expanded the ZIP file.
            > 3. Renamed /bux folder to /auxx (/aux is not allowed)
            >
            > It turns out the this folder only contains a separate GIF builder utility,
            > so I think this is not a critical part of the software.
            >
            > -- Paul
            >
            >[/color]
            Oh, you also have to modify setup.py, to change the reference to slut.aux
            package to slut.auxx.

            -- Paul


            Comment

            • Ido Yehieli

              #7
              Re: SLUT distibution mangled?

              ok, Thanks Paul!

              Comment

              • Rob Wolfe

                #8
                Re: SLUT distibution mangled?

                Actually when you remember the ancient history of Windows and MS/DOS
                you will see why. That filename, and a lot of others (as noted by
                Fredrik) are legacies of that time. They were special filenames (think
                "/dev/null") that related to specific devices.

                Gives us a good example of one of the little "gotchas" involved in
                cross platform development.

                Rob

                Comment

                Working...