Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [higgins-dev] Can we cvsignore lib?

So, that's a valid bitch even if you're not going to fix it.

The hurdle I see is that we have no permission to redistribute the jar files on which we depend.  Ideally, we would have CVS populated with the dependency jars we need.  An even better ideal would be the existence of a reliable jpackage-like service, but there's not.

We have floated the idea of creating configure-like scripts that auto-fetch jars from the appropriate places, but that hasn't been done because either a) no one has had time or felt like taking it on, or b) we're worried that to get some jars, a user is required to acknowledge a license agreement.  I can't remember which is the more popular excuse.


 
>>> "Ben Laurie" <benl@xxxxxxxxxx> 09/05/07 11:13 AM >>> 
On 9/5/07, Jim Sermersheim <jimse@xxxxxxxxxx> wrote:
> It seems like we're a long way from storing all dependency jar files in CVS.  Until that day comes, does anyone object to adding "lib" to the .cvsignore at each project root?
>
> On the plus side, this would allow anyone using a link- capable OS (*nix) to create a "lib" link to a common lib directory.  This would save lots of frustration in copying jar files around as dependencies change over time.
>
> On the minus side, people would have to create a lib directory (or link in the case above).

I realise I'm doing none of the work, so I have no right to bitch, but
can I just comment that this is a really unfriendly way to manage your
open source project?

When I check an open source project out of its CVS tree, I expect to
be able to build it by doing, at worse, the moral equivalent of:

autoconf
,/configure
make

in other words, get the configuration generator to do its magic for my
local environment, then run the generated configuration script and
then build.

If you think that people have to create lib directories or link them,
then make your configuration script do that for them. Don't make them
create them by hand, that's just mean.

BTW, I'd suggest the link :- )

> I don't think creating a lib directory is all that bad since we already require people to populate it today (which is much more work than making the directory).
>
> If no one objects, I'd like to do this within the next day or two.
>
> Jim
>
>
> _______________________________________________
> higgins- dev mailing list
> higgins- dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins- dev
>
_______________________________________________
higgins- dev mailing list
higgins- dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins- dev



Back to the top