Hi,
I would like to move the package biopython-py from /sci to /libs/
pythonmods. Is there an easy way to do this in cvs, or should I
remove, add and re-commit it?
thanks,
- Koen.
-
Check out the new SourceForge.net Ma
Good day,
Just trying to compile sylpheed, same error with sylpheed ssl :
http://paste.lisp.org/display/53951
I googled but didn't find a solution or a clue.
I'm on 10.4.11 PPC, latest Fink
Cheers,
--
Pierre-Henri Lavigne a.k.a. Åkeson Chihiro
Front end developer, Fink member
http://my.opera.
On Thu, Jan 10, 2008 at 06:22:32AM -0500, Koen van der Drift wrote:
> Hi,
>
> I would like to move the package biopython-py from /sci to /libs/
> pythonmods. Is there an easy way to do this in cvs, or should I
> remove, add and re-commit it?
There's no such thing as "move" in the world of CVS.
That's what I thought too, thanks. I guess the history of the file will be
lost, though, but I don't think that's a big issue. Should I worry about local
deb files that are already in the /sci tree, or will fink recognize those even
though they are in a different location?
- Koen.
-Origi
Well, not "lost" per se, since cvs keeps a history of dead files, too.
If you've made a commit note about having relocated it then it
shouldn't be too hard to figure out.
I don't think the section change will really have much impact on users
that already have .deb files.
On Jan 10, 2008 11:02 A
Concurred. Fink checks the /sw/fink/debs/ symlink, which points to the
.deb where it was created (parallel to the .info), so even if the
.info moves, the symlink still works.
dan
On Thu, Jan 10, 2008 at 11:15:59AM -0500, Alexander Hansen wrote:
> Well, not "lost" per se, since cvs keeps a history
On 10-Jan-08, at 10:12 , Pierre-Henri Lavigne wrote:
>
> Just trying to compile sylpheed, same error with sylpheed ssl :
> http://paste.lisp.org/display/53951
>
> I googled but didn't find a solution or a clue.
> I'm on 10.4.11 PPC, latest Fink
I just finished building sylpheed on 10.4 PPC. It bu
Kevin Horton wrote:
> On 10-Jan-08, at 10:12 , Pierre-Henri Lavigne wrote:
>> Your command has the following flags, missing from mine:
>
> -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DXNO_MTSAFE_UNISTDAPI
>
> I don't know if these additional flags are relevant, as I have not yet
> found them in
