Pisilinux3/pisi
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Daha önce kafamı karıştıran şeyi buldum.

Browse Source 
actionsapi'nin build/install dizini dışında başka bir konumdan dosyaya/dizine
ihtiyaç duymaması gerekiyor. Dolayısı ile libtoolize() fonksiyonu yanlış.
Bir yama yapılacaksa, bırakalım PisiBuild işini yapsın...
This commit is contained in:
Barış Metin
2005-06-16 20:51:40 +00:00
parent a8eff5a961
commit edd6a0bfe5
1 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pisi/actionsapi/libtoolize.py
+4 -6
View File
@@ -1,16 +1,14 @@
#!/usr/bin/python #!/usr/bin/python
# -*- coding: utf-8 -*- # -*- coding: utf-8 -*-
import os,sys import os
#sys.path.append('..')
from pisi.context import Context
def libtoolize(): def libtoolize():
''' FIXME: Düzgün hale getirilecek ''' ''' FIXME: Düzgün hale getirilecek '''
''' patch source with ltmain patches ''' ''' patch source with ltmain patches '''
# no need to create a context for calling static functions # This is wrong! Action files should only operate on the build
# currently staticmethods doesn't work in Contex but this function isn't used to ;) # directory. And shouldn't depend on external files. If a patch is
# need to be applied it is PisiBuild's job to do it!
os.system('patch -sN < ' + Context.lib_dir() + '/portage-1.4.1.patch') os.system('patch -sN < ' + Context.lib_dir() + '/portage-1.4.1.patch')
os.system('patch -sN < ' + Context.lib_dir() + '/sed-1.4.0.patch') os.system('patch -sN < ' + Context.lib_dir() + '/sed-1.4.0.patch')