On 10/05/2010 04:44 AM, Dale wrote: > dhk wrote: >> What should I do about dev-util/autotoolset? I use it every day for a >> project, but today it looks like I'm being told to remove it. What is >> the alternative? >> >> In my package.keywords file I have "dev-util/autotoolset ~amd64" >> unmasked since I use autotools for a project. >> >> After the output of "emerge -uDNp world" this morning the following >> message is displayed. >> >> !!! The following installed packages are masked: >> - dev-util/autotoolset-0.11.4-r1 (masked by: package.mask) >> /usr/portage/profiles/package.mask: >> # Diego E. Pettenò<flamee...@gentoo.org> (04 Oct 2010) >> # on behalf of QA team >> # >> # Ironically, it is misusing autotools (bug #255831). It was >> # added in 2004 and never version bumped since; autotools >> # have since evolved a fair amount, while this is based >> # still on automake 1.6. Avoid keeping it around. >> # >> # Removal on 2010-12-03 >> >> For more information, see the MASKED PACKAGES section in the emerge >> man page or refer to the Gentoo Handbook. >> >> As stated above, what should I "Avoid keeping it around?" Is it >> autotoolset, automake 1.6, ...? Also, what's getting removed on >> 2010-12-03? If autotoolset is removed, what should be used to build >> projects? >> >> Even though I have autotoolset installed, search shows it as being >> masked. >> >> # emerge --search autotoolset >> Searching... >> [ Results for search key : autotoolset ] >> [ Applications found : 1 ] >> >> * dev-util/autotoolset [ Masked ] >> Latest version available: 0.11.4-r1 >> Latest version installed: 0.11.4-r1 >> Size of files: 1,133 kB >> Homepage: http://autotoolset.sourceforge.net/ >> Description: colection of small tools to simplify project >> development with autotools >> License: GPL-2 >> >> >> What to do now? >> >> Thanks, >> >> dhk >> >> > > Here are a couple options. Subscribe to -dev and see if you can take > over maintaining the package. Then do whatever needs to be done to get > it updated and keep it stable. If you can do that, they could let the > package stay in the tree. > > Next option, copy the ebuild to a local overlay and maintain it there. > Keep in mind, doing this is about the same as above except it affects > just you. You do all the work locally. > > One other option, use different tools to do your project. I don't know > anything about autotoolset or what it does but there may be better tools > to use. > > If you don't do one of the above, autotoolses ebuild will be removed and > you will eventually have to do something because there will be no more > updates. Which appears to be the case now anyway. No updates since 2004. > > There's some options. Someone else may have a couple more. > > Dale > > :-) :-) >
This isn't good. It sounds like my project is in deep trouble since the whole build and distribution is done with the autotools. Taking over and maintaining the package is an option, but I think it will be gone before I can get up to speed on it. I wonder how many developers out there have an interest in it if it's that antiquated. Personally I think it's a great tool. Anyone know what other tools are being used to build and distribute programs with dependencies? Thanks, dhk
