[sage-devel] Re: Package management and versioning

2008-07-22 Thread mabshoff
On Jul 21, 6:18 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: Hi Vincent, > > > Quick and very dirty : 'find . -cmin -5' (files modified less than 5 > > > minutes ago). > > > Not even close :). There are packages that install in less than 10 > > seconds. > > That one was a joke, of course.

[sage-devel] Re: Package management and versioning

2008-07-21 Thread [EMAIL PROTECTED]
> > Packages need to be configured with --prefix=$SAGE_ROOT/local, > > installed with DESTDIR=somewhere, and then somewhere/$SAGE_ROOT/local > > has to be renamed to $SAGE_ROOT/spkg/graft/packagename-v.er.si-on > > before graft (or whichever one) is called to put the links in place. > > I am more

[sage-devel] Re: Package management and versioning

2008-07-21 Thread [EMAIL PROTECTED]
> > Quick and very dirty : 'find . -cmin -5' (files modified less than 5 > > minutes ago). > > Not even close :). There are packages that install in less than 10 > seconds. That one was a joke, of course. I have used it occasionally for a punctual problem, but it's not for packaging. > I am not

[sage-devel] Re: Package management and versioning

2008-07-21 Thread mabshoff
On Jul 20, 4:21 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: Hi, > > OK, so who knows a clever way to detect which files were added/changed > > in a directory structure? > > Quick and very dirty : 'find . -cmin -5' (files modified less than 5 > minutes ago). Not even close :). There are p

[sage-devel] Re: Package management and versioning

2008-07-20 Thread mabshoff
On Jul 20, 2:39 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi folks, Hi Vincent, > Looking at the way that sage builds and installs its packages, I > didn't see an easy way to remove an optional package (say in case it > breaks something, or you don't need it anymore) ; has it been > c

[sage-devel] Re: Package management and versioning

2008-07-20 Thread [EMAIL PROTECTED]
> OK, so who knows a clever way to detect which files were added/changed > in a directory structure? Quick and very dirty : 'find . -cmin -5' (files modified less than 5 minutes ago). Quick and dirty : ls -lR > before ; make install ; ls -lR after ; diff -u before after | sed -e 'whatever_to_pr

[sage-devel] Re: Package management and versioning

2008-07-20 Thread [EMAIL PROTECTED]
> > There is also a lot of code that does not use configure && make && > > make install. How is that dealt with? What about python packages? Or > > do you only want to deal with optional packages? > > Yes, I think he definitely claims to *only* want to deal with optional > packages. I don't ! On

[sage-devel] Re: Package management and versioning

2008-07-20 Thread mabshoff
On Jul 20, 3:27 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Sun, Jul 20, 2008 at 11:59 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > On Jul 20, 2:39 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > wrote: > >> Hi folks, > > > Hi Vincent, > > >> Looking at the way that sage builds and inst

[sage-devel] Re: Package management and versioning

2008-07-20 Thread William Stein
On Mon, Jul 21, 2008 at 1:00 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >> > Yep. Although the "keeping track of the package manifest" would still >> > help a bit there - no protection against clobbering files though. >> >> What about literally doing that? If one installs a package foo-0.

[sage-devel] Re: Package management and versioning

2008-07-20 Thread [EMAIL PROTECTED]
> > Yep. Although the "keeping track of the package manifest" would still > > help a bit there - no protection against clobbering files though. > > What about literally doing that?  If one installs a package foo-0.1.spkg, > then a file > >     spkg/installed/foo-0.1 > > appears.  It could contain

[sage-devel] Re: Package management and versioning

2008-07-20 Thread William Stein
> Yep. Although the "keeping track of the package manifest" would still > help a bit there - no protection against clobbering files though. What about literally doing that? If one installs a package foo-0.1.spkg, then a file spkg/installed/foo-0.1 appears. It could contain a list of all t

[sage-devel] Re: Package management and versioning

2008-07-20 Thread François Bissey
On Mon, 21 Jul 2008, mabshoff wrote: > > Packages need to be configured with --prefix=$SAGE_ROOT/local, > > installed with DESTDIR=somewhere, and then somewhere/$SAGE_ROOT/local > > has to be renamed to $SAGE_ROOT/spkg/graft/packagename-v.er.si-on > > before graft (or whichever one) is called to p

[sage-devel] Re: Package management and versioning

2008-07-20 Thread William Stein
On Sun, Jul 20, 2008 at 11:59 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > On Jul 20, 2:39 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: >> Hi folks, > > Hi Vincent, > >> Looking at the way that sage builds and installs its packages, I >> didn't see an easy way to remove an optional package

[sage-devel] Re: Package management and versioning

2008-07-20 Thread William Stein
On Sun, Jul 20, 2008 at 11:39 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi folks, > > Looking at the way that sage builds and installs its packages, I > didn't see an easy way to remove an optional package (say in case it > breaks something, or you don't need it anymore) ; has it been >