cvs commit: ports/devel Makefile

[Ruslan Mahmatkhanov]

Alexey Dokuchaev wrote on 26.12.2011 12:33:
> On Mon, Dec 26, 2011 at 11:31:33AM +0400, Ruslan Mahmatkhanov wrote:
>> Mark Linimon wrote on 26.12.2011 03:11:
>>>   
>>>   This badly-named port is not being propogated through our csup/cvsup
>>>   machinery, and until this is fixed, various tools will be broken on
>>>   various people's systems.
>>>   
>>>   Hat:            portmgr
>>>   
>>>   Revision  Changes    Path
>>>   1.4772    +1 -1      ports/devel/Makefile
>>
>> Hmm, i thought that this rule applies only to files, not to
>> directories.. So would you please repocopy it to, say, py-kss-core?
> 
> It always suprised me how could people come up with dot-containing port
> names in the first place...  Not to mention that this `.core' issue had
> bitten us already in the past.
> 
> ./danfe

Alexey, this naming was discussed [1] _before_ i ever starting to add
all this ports and there was no strong objections (and this is not
prohibited anywhere in Porters Handbook, Committers Guide etc) about
this. The point is to name it as close as upstream do - the same policy
apply to p5 ports, so why there should be exception for py- ports?

About .core issue - i'm apologize. It's true. I was sure that this
restriction is just for files, not for directories.
So, as some bearded TV-character said, "Please understand and forrrrgive".

[1]
http://lists.freebsd.org/pipermail/freebsd-ports/2011-September/069877.html

-- 
Regards,
Ruslan

Tinderboxing kills... the drives.